CGS Web Designs

@rajkiranb what I’d like to know is why doesn’t the plugin respect the theme settings before overriding with a default value of 0? That’s not the type of UX experience anyone would expect.

It appears the first 2 items were fixed with the 2.0.3 release. The issue with section (now Advanced Row) blocks seems to be isolated only to those which have a gradient style overlay and I’ve been told they’re working on fixing it.

Still seeing Advanced Columns ignoring reverse on mobile settings which is frustrating (minor though compared to everything else).

I also am discovering that Spectra sets the default editor block spacing to 0 px – why in the world would anyone even think to do that? Shouldn’t that be controlled by whatever theme is in use? Holy crap the editor looks like garbage out of the box because of this.

I’m seeing this exact same thing if you look at my previous post here https://www.ads-software.com/support/topic/all-kinds-of-styling-issues-after-update/

That’s what I found with the font colors when using the Info Box inside a Cover block.

It’s actually in the Cover block where the text and alignment are wrong for the Info Box blocks. It appears that the styling is forced to inherit the Cover block settings instead of using what is configured in the block (found this looking through CSS in developer mode).

I’ll submit a ticket with all of the issues for your reference.

in 15+ years of WordPress design I’ve never had the rug pulled quite like this

I guess you’ve never used Elementor huh? ??

This is one of the reasons why I try to vary my site builds. It’s easy to fall into a flexible theme like Astra and UAG and then build everything with it… but then if you have to manage all those sites, all your eggs are in a single basket. It’s best to get your site builds split between different themes and block plugins sometimes so that maybe when the rug pulls, only half your customers are affected – and it helps keep your skills from getting stale using the same tools over and over.

Also I noticed that when trying to switch to Containers – padding on mobile seems to ignore the plugin settings. It’s just always zero instead of what is set in the plugin settings screen.

All of my sections changed to Advanced Row when I updated – which doesn’t have the same features. A lot of my sections have background images which apparently just go away after the update. Font colors inside sections seem to ignore settings and just do their own thing as well. Had to roll back my update to 1.x.

I’m hoping you don’t have to convert anything – the general consensus in the forums seems to be that a lot is messed up. The Section and Advanced Column blocks were really front and center for a LOT of websites – I’m not sure what BSF had in mind when it came to deprecating them, but I think it’s pretty obvious at this point, they may need to backtrack.

And honestly, from a critical eye… do you really trust ANY developer to not make breaking changes? That’s like a feature of developers is that they break stuff lol! You can go through all the effort of finding something new, but at the end of the day it’s just another developer who will one day make a major release version that kills everything.

I feel your pain. I didn’t use the Advanced Columns much but I did make heavy use of their Section block which has had similar breaking changes.

I’ve dealt with their support though in the past and in general they do address every concern – so I have restored my affected sites to their previous state and will just wait until more updates are released. I’m confident they will make it work – just will take some time and we need to provide detailed feedback on what we’re seeing so they have all the information they need.

Thanks, I haven’t tested the CSS you provided, but I am fine waiting for a working update. It is not yet that critical. Thanks!

I use it on 2 sites – https://cgscomputer.com and https://allisonspoppinpapa.com and both are showing the animations on an actual mobile device (iPhone 13 Pro).

Hi, I’m going to mark this as resolved. While I don’t know for certain the cause (possibly litespeed abort but didn’t have enough time to fully test), my hosting company just migrated to a new server overnight and the scans are now working.

The plugin is not compatible with PHP8. If you’re running that, it’s the cause of your issue. I’ve had a paid ticket open with the developer about this for over 6 months and they’ve never even acknowledged the ticket.

The developer hasn’t updated the plugin to be compatible with PHP 8. That’s the issue you’re seeing.

Thanks, I have the setting for skipping the cache enabled as I mentioned in the initial report. I have added the URL to my cache exclusions and will report back.