Home>Support>Transferring Page Builder content from one installation to another breaks the “Update” feature

Transferring Page Builder content from one installation to another breaks the “Update” feature

Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].

So this is quite an odd problem and I’m not sure what’s causing it.

I’ll try to explain this as best as possible.

I have an offline installation of WordPress 4.3 on my computer that I have been using to design a theme and build an entire site. I found the plugin Page Builder and love how easy is is to build responsive pages directly inside WordPress.

It was working perfectly fine until I transferred everything over to my “live” WordPress site. I used the All-In-One WP Migration plugin to transfer all files/database/plugins/themes to my live WordPress site.

However, one of the pages I used the Page Builder on is now broken and un-editable. If I try to make changes to any part of the page using the Page Builder and I click on either “Preview Changes” or “Update” it immediately redirects to a blank “post.php” page. After that all of the styling for that page is broken. And when I go back into the editor, it’s all just jumbled code that I can’t understand and it no longer opens in the Page Builder view. If I switch to that view it just takes everything and puts it into one row.

Any ideas of what is causing this? It’s driving me crazy because I cannot edit that page at all until this is resolved.

Thanks,
Austin

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 9 years, 9 months ago Andrew Misplon
    Hi, I Work Here

    Hi Austin

    Sorry to hear about the hassle. We believe character encoding might be the challenge. You can perhaps try again ensuring the export and import is done using UTF-8.

    Alternatively, Duplicator handles this job really well:

    https://wordpress.org/plugins/duplicator/

    Let us know how you come along.

  2. 9 years, 9 months ago Austin Gardner

    Hi Andrew,

    Thanks for the response. I actually ran into a problem with Duplicator as well. So instead I decided to just uninstall Page Builder from the new site and reinstall it and then create the page all over again.

    However, about halfway through the process when I click update it gives me the same error. So I’m starting to think there is a bug or something with the plugin. Any other suggestions you might have?

    Thanks!

  3. 9 years, 9 months ago Andrew Misplon
    Hi, I Work Here

    Phew, ok. If you go with the manual move then you can just do a WordPress Import/Export. XML moves Page Builder data without hassle. That’s available to you from Tools > Export and Tools > Import. The import note here is that the same plugins and widgets must be installed before running the import.

    How did you move the content itself if not with Duplicator?

    What was the Duplicator issue?

    Have you gone to Settings > Permalinks and clicked Save on the new site?

  4. 9 years, 9 months ago Austin Gardner

    Hey Andrew, great news!

    After experimenting around with it a little more I realized that even the standard WordPress Text/Html widgets were not saving correctly and giving the same error.

    It turns out that there was a certain security parameter on the server I was hosting on that was causing these issues when WordPress was trying to POST to the server. I talked to the hosts of my server and they got it sorted out and everything works great now!

    Thanks for your help!

  5. 9 years, 9 months ago Austin Gardner

    Actually, I take that back. :(

    That fixed another issue I was having but I’m still getting the same error with Page Builder.

    A couple things I’ve noticed. When creating a new page with Page Builder, after a certain amount of rows have been added with content, that’s when the error happens where if I click on “Update” in WordPress it redirects to a blank ‘post.php’ page and breaks the layout. If just add a couple rows with content, it updates just fine.

    I decided to run Fiddle this time to try and diagnose exactly what error was being caused when I tried to update the page.

    It returned a 504 error at /wp-admin/post.php and gave the following message: “ReadResponse() failed: The server did not return a complete response for this request. Server returned 33,048 bytes. “

  6. 9 years, 9 months ago Andrew Misplon
    Hi, I Work Here

    Thanks for the long wait. This sounds like it could be a memory related error. Can you confirm that WP has at least 256m of PHP memory available to it?

  7. 9 years, 9 months ago Austin Gardner

    Yes, it does have 256m of PHP memor available. I have a feeling it could be another server related issue though as I have narrowed it down to not just be Page Builder. Another similar plugin is giving the same issue.

    I’ve contacted my host to try and get this sorted out. I’ll post back here with an update when I have one. But like I said, I’m pretty sure at this point it isn’t related to the Page Builder plugin. :)

  8. 9 years, 9 months ago Andrew Misplon
    Hi, I Work Here

    Thanks for your feedback. Hope you’re able to get it resolved.

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More