PAGE BUILDER ISSUE WITH 5.5 UPDATE | REQUESTING PREVIOUS VERSION REVERT |
Hello, With the new update with everyone on the support forums reporting issues, could SiteOrign please create a patch or post a prominent link to revert back to the previous version until a patch can be built?
The solutions I am seeing have in majority been to switch to an alternate theme and try turning off plugins one by one, but this loses a majority of the built content on our site and the Twenty Twenty theme would take days to convert to our current Bento theme build. When previewed, this switch makes it an unacceptable solution due to the time it would take. We use your sliders and widgets, etc for a lot of our content and rely on this to work to make changes to our site.
We are unable to edit or see the text editing in the Backend Mode of editing, and simple coding like changing a link on a button, for example, will not save…the buttons do not work.
Love the plugins and hope there is a solution fast- we need it!
Thank you for your time,
Alexandra
Ferrin Contemporary
Hi Alexandra
Thanks for reaching out.
You can easily rollback any plugins using https://wordpress.org/plugins/wp-rollback/. We’re working on an issue with lazy loading and sliders but besides that, we don’t have any open WordPress 5.5 issues. In all of the cases we’ve seen so far, Page Builder isn’t working due to other plugins or themes producing errors that stop anything else on the page using JavaScript.
The point of a plugin conflict test is to locate a working baseline. If you can locate a working baseline you’d then add your theme and plugins back until the issue reoccurs, thereby locating the conflict. This information often gets confused and lost in the process which is why we often start with the first part of the test. In all of these cases, we use the word “temporarily”. Temporarily switch to Twenty Twenty. Please, find the full test below, let us know how it goes. Thanks.
—
This sounds like it could be a plugin conflict issue. Can you try disabling all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.
If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.
Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.
If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.
Regarding the time it would take. The initial step should only take a minute or two. Temporarily switch to Twenty Twenty and deactivate all plugins not authored by SiteOrigin, does the issue resolve? If so, you know you have a conflict somewhere and can schedule a time when your traffic is low to work on it. If you can find a working baseline you’d first add your theme back, test, if the issue doesn’t reoccur then you’d reactivate your plugins one by one, checking for the issue after each activation. If you want to use a Maintenance Mode plugin, you can do so and leave that enabled throughout the test. Hopefully, this clears up how a conflict test works.
Hi Andrew,
I really appreciate the email and wasn't expecting such a quick response,
how wonderful and thank you for the suggestions. I was thinking about the
Wordpress 5.5 update I just did and realize I miswrote- it is indeed the
6.2.0 Pagebuilder and the WordPress update doesn't seem related-sorry for the bad info. Thank you for the link to the rollback, also. I believe the issue is with the Site Origin Plugins and Widgets so it makes sense that something is amiss with the plugins working with others. Has anyone reported the menus not displaying or not being able to save changes made?
I will certainly try these steps as you suggested- thank you for outlining.
Will Site Origin be fixing how its plugins work with others or do I have to figure out which one is the "bad" one?
Thank you,
Alexandra
Hi Alexandra
Sure, no problem.
Has anyone reported the menus not displaying or not being able to save changes made?
Not that I can think of. The first part of the baseline test would be helpful to see if a working baseline can be found. Do these issues resolve with Twenty Twenty and only SiteOrigin plugins activated? You can restore the site once that step is done.
Will Site Origin be fixing how its plugins work with others or do I have to figure out which one is the “bad” one?
You’ll have to figure out where the conflict is arising.
You can also try checking the browser console when the issue occurs, errors are printed in red, if there is an error, hover over the file path on the right to see the full path, if it’s a theme or plugin the name will be included in the path. Here is how to check the console https://wordpress.org/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis. Doing a plugin conflict test is a less technical route.