I built a site on a test server using the Create them by Themetrust. I moved the site to the new server using WP Clone by WP Academy and WP Migrate DB. Everything seemed fine until I tried to make a change to a page. I can no longer edit Pagebuilder content. The server belongs to my client and is hosted thru GoDaddy. I am trying to avoid asking for access to their GoDaddy account. And I tried using Duplicator, I was able to create a package but am not able to use the installer php file. When I try to open it in a browser it either won’t open (Safari) or only displays as source code (Chrome). Please help!
Page builder no longer working
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi Paul,
Could you please clarify what the issue is? “I can no longer edit page builder content” is extremely vague and doesn’t tell me anything that will help me fix your issue.
You need FTP access to their server for Duplicator work. I’m unable to provide support on Duplicator issues but I can tell you right now – that’s the tool we recommend for migration and I’ve never had a failed migration with it. :S
Thanks Alex,
When I edit a page with builder content, the page builder interface is missing and the content is displayed as text.
When I create a new page, the menus/icons are present and I can click to add a row or use a prebuilt template, etc. but once the dialogue opens clicking on the button to insert or add a prebuilt template does nothing and I am forced to click the close X button to exit the dialogue.-PS
Hi Paul,
Hm. That sounds like a failed migration. I think your best course of action would be to work out what’s going wrong with Duplicator (which, again, I can’t really help with)
I didn’t use Duplicator. In case you get more requests like mine, here is the solution from Themetrust:
Please try deleting the pagebuilder plugin and installing it from here: https://wordpress.org/plugins/siteorigin-panels/
Kind Regards,
-Roch
Hi Pauls92509,
Ah – didn’t think this was a fork issue. So they’re no longer recommending their fork? Thanks for the information.