I have the same issue!
Just updated tho 2.0 and there is no support for Sections and Advanced Columns.
I have clients complaining they are not able to edit their content.
Please help to resolve this issue!
We have the exact same issue with backwards compatibility as @somewhatmedia has mentioned above. Especially as we’ve used Advanced columns on every site we’ve built for the last 3 years! Backwards compatibility is really needed or at least some sort of solution other than just dropping it is found, please look into ASAP! Thanks, The Blaze Team
@stelat & @blazeconcepts – for now, you can rollback in the Spectra settings to the last version of UAGB as a quick, short-term fix but this could turn into a massive issue for us as we’ve been using Astra & UAGB exclusively for years now and have some immensely complex sites.
Same issue. Restored site backup, will wait until this is sorted before updating UAGB again.
I asked in the Spectra Beta group back in April if it would be backwards compatible and had confirmation that it would be.
From one of the co-owners of BSF:
“1. Since the current Spectra version is beta, there are a few known backwards compatibility issues with legacy blocks. They will be resolved in the next beta version.
2. You can continue using legacy blocks on existing website. On new websites, legacy blocks won’t show up.
3. There’s an easy upgrade path available. Gutenberg offers “covert block” feature, which can be used 😀”
I see now that they changed the name of the function Advanced column to Container so the function is not gone but when you update to the newest spectra then the content inside the advanced column get stuck and cannot be moved out the column. So please becareful to update to soon!
First move the content first and then you can update the addon and then move the content back in the new Container function, this is my workaround for now.
Still this is a disaster for me because it is alot off work to be done!
I hope that Brainstorm has a better transition proposal for us to make the change quicker for all our websites!
-
This reply was modified 2 years, 1 month ago by
Marcel.
@somewhatmedia – yes, I already rolled back the version on some of my sites, but thank you for suggesting it!
However, where can I find this “covert block” feature?
If it is misspelled and they mean the “Attempt block recovery” feature, I don’t have this option with the new version, only “Keep as HTML”
@stelat Those comments were made back in April so it’s possible things have changed. I have the same problem – no way to “convert” from UAGB Sections / Advanced Columns into the new Container type – only either to leave it as it is or convert to HTML which is very irritating.
My company’s website uses a lot of advanced columns and everything is broken in the editor and not displaying right either. I rolled back the plug-in but I would really appreciate an option to transition to 2.0 version so I don’t have to stay on an outdated version forever. A warning about the update being this major would’ve been cool as well.
-
This reply was modified 2 years, 1 month ago by
saskia85393.
Exactly same issue. All pages with advanced columns in back end editing now showing errors, resolved by rolling back plugin to 1.x.
Crazy stuff. It also did some minor changes to the frontend. Need to roll back 10+ websites manually now.
New version 2.0.1 is out which fixed the problem 🙂
Hello @cacobanton , @drquesh , @saskia85393 , @somewhatmedia and @stelat ,
Sorry for the inconvenience caused to you.
I see you have an issue with the deprecated blocks after updating to the current Spectra 2.0.0 version.
It has come to our attention that the old users updating to the new Spectra version are experiencing this issue.
To fix this, first, you’ll need to update the Spectra plugin to the latest version i.e. 2.0.1, and after that, you’ll need to add this ?spectra_old_user=yesafter your URL from the dashboard section as shown in this video and you just need to check the editor and you can see that the issue is fixed.
I hope that helps.
@swetakumari
Thanks for the quick patch! This has resolved my issues.
Many thanks,
Matt
@swetakumari
Hello Sweta
Thank you for the quick fix, however how I am supposed to do this fix on packaged themes?
Obviously, asking new clients to add this ?spectra_old_user=yes to their URL looks unserious.
Does this mean that I have to re-build all my themes to meet your updated version?
