Hi,
So I am on a project team, and our goal was to update a website. Throughout the project, we have been using Pagebuilder to add information, images, and other additions to improve the site. Around four weeks ago, pagebuilder was replaced with Beaver Builder, another pluggin similar to pagebuilder. Now, we cannot do anything to modify the site, which is a major issue. We have contacted Beaver Builder, but also want to see if anyone here can help. Thank you so much in advance!
Thanks,
Mia Lu, Project Manager
Hi Mia
Pages built with Page Builder by SiteOrigin won’t be editable in the Page Builder interface if you’ve deactivated Page Builder by SiteOrigin. You could build new pages with Beaver Builder but it isn’t possible to migrate Page Builder by SiteOrigin pages to another Page Builder.
Thank you so much for your quick response! However, our project team did deactivate Beaver Builder and reactivate Page Builder. It completely changed the format of the site, and we still could not edit or modify anything on the site.
It’s worth considering rolling your site back. Most hosts keep backups for seven days.
You can also try running a plugin conflict test, steps below:
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.
Do you think that deactivating the plugins may permanently affect the site? We are trying to be very cautious and I am not sure if the site can be restored if the plugins are reactivated.
Hi. No, not at all. The steps described are standard troubleshooting procedure.