Oh weird. I saw it on images and assumed it’d be on divs but didn’t see it. But just double checked and it is there! Note to self, I shouldn’t trust my 5pm Friday eyes!
I like this. I’ve been using adjacent (I thought I’d prefer split but adjacent feels better for me) - but when I then switch to my laptop it takes up too much of the screen (the original sidebar already pushed my macbook air 13in into the smaller laptop screen breakpoint so it was a pain as any changes are then just at that breakpoint). So being able to toggle would be great.
We can think on having an ability to hide the outline in those mode. It would probably work more like a toolbar button like in modal mode. Since the buttons on the top are really acting more as tabs.
RC1
- Updated - Padding and spacing fixes on settings
- Updated - Content storage has a different UI look
- Updated - Starter section svgs updated and made larger in these sections
- Updated - Updated Sub group descriptions in the settings
- Updated - Updated descriptions in the Dashboard Settings
- Updated - better starter icons layout on smaller screens
- Bugfix - Toggle position on Global Settings not correct in Chrome
CSAI Beta3
- Feature - Themeco Built in prompts can be turned off
- Feature - Response time is hidden unless you turn on the CSAI preference “Response Time”
- Updated - Updated provider descriptions
- Updated - Permission checked properly on edit with ai button
- Updated - Slight Redesign and tune-up of UI
- Updated - Less padding on Edit with AI button on inline inputs
Unreleased in 6.6.11
- Updated - Decorative images will set the alt tag as empty instead of removing the attribute entirely
- Bugfix - Grabbing a cookie before it was set would give a warning
- Bugfix - WooCommerce Dynamic Content product grabbing would sometimes crash
2 Likes
Hmm, new Pro is breaking my elements where I used the padding-top trick to get aspect ratio on a Div. but there is something more to it, and I am digging deeper to understand what setting is causing it. I will get back when I find the culprit.
Edit, found it. It is described in this thread:
I have a background image set to the featured image ({{dc:post:featured_image_id}}) in My header. This doesn’t get picked up in the RC1
@Misho Sent you a message, we’ll get that fixed in RC2.
@arnoldmeulenbeld I actually don’t see this happening, could you create a new topic and send me more info?
@charlie I fixed it by replacing the Backround Image with the Element. Don’t ask me why, but it works.
Image Element that is
@charlie I had the same issue with a site using beta where featured image wasn’t showing for a blog archive layout I had built. It was on the RC1 beta build but as the site was live I had to downgrade to the live version of Pro which fixed the issue.
I realise that’s not much help but it does show the problem wasn’t just @arnoldmeulenbeld
Unfortunately due to the issue with loopers and backgrounds images we’re probably going to have to remove breakpoint images for the Advanced Backgrounds till we can address this. The problem is you can’t use CSS var() with the CSS url() so it results in the background images being broken when using a looper. We’ll try to address this in Pro 6.8 whether it be from removing our usage of var() internally (which ends up creating a lot of style="--dc-var: imageUrl" attributes anyway) or another way to fix. Sorry about this.
1 Like