Home>Support>Can’t Update Pages with So Page Builder Enabled

Can’t Update Pages with So Page Builder Enabled

I have a similar problem as other recent posters: I can’t update any pages when SO Page Builder is being used.

So far I’ve:
— Ruled out a cache issue
— Ruled out an issue with all non-SO widgets
— Uninstalled and reinstalled SO Page Builder and SO Widgets Bundle (would have tried an older version but could not find one available for download). No dice.
— Ruled out a theme issue (happens even with the 2020 theme)

Hope y’all find a solution soon. Watching support basically blame other posters’ issues on specific quirks to their site (e.g. page size) is disheartening. In the meantime, I’m trying to eliminate any SO-dependency on a staging version of my site so I can just remove it.

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

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

    Hi Jake

    That really isn’t a fair characterization of the case I just worked. The user in question wasn’t able to update the page, the changes weren’t being saved, the page wasn’t completing its saving within Page Builder. The page was password protected meaning you couldn’t see the size of the page without logging in. Blending a request for assistance with your last paragraph really isn’t ideal in a free support scope. To confirm, that case was not the same as changes not reflecting. The page in question was enormous, with dozens and dozens of Accordion widgets. It’s highly likely that the processing time for the page save reached the server maximums. Given that it was far more practical to break the page up for the sake of usability, it was an easy solution to the problem, a solution that the user was happy with. No blame was assigned. The page size was an observation and a likely cause. But again, not the same issue.

    The previous case of this nature that I worked was due to a user merging Page Builder data directly into Elementor, something neither plugin is built to do. We solved the case.

    Please, send a link to a page concerned and we’ll take a look.

  2. 4 years, 4 months ago Andrew Misplon
    Hi, I Work Here

    Unless of course, the issue you’ve run into is widgets not saving in the WordPress admin, then it is the same issue as the previous poster. If you can clarify, that’ll be helpful. Thanks.

  3. 4 years, 4 months ago jakecroach

    Hi Andrew,

    Thanks for the reply and for putting up with my frustration.

    No, the widgets are saving in the admin, but they are not presenting on the page unless I disable SO Widgets and PageBuilder.

    Here is the page: https://flyfortheculture.org/about-us/

    Thanks,
    Jake

  4. 4 years, 4 months ago Andrew Misplon
    Hi, I Work Here

    Thanks for your understanding, ideally, I should have taken a break before replies. What I should have said is at the moment I know there have been a series of content not updating threads. Unfortunately, we haven’t yet found a common cause or bug that we can log. We’re actively developing our plugins, if we find an issue, we’ll do our very best to fix it as quickly as possible. We certainly don’t want you to have an experience like this. I’m sorry about the hassle.

    Is your staging site displaying the same issue or is it already quite different? To speed things up, I’d be happy to log in and run a few tests, assuming it would be ok to take your site’s plugins offline for a few minutes (at most). If it is an issue, I could use a maintenance mode plugin. I asked about the staging site because that’s an easier place to test if it’s the same as the production/live site.

    Would it be possible for you to create a temporary admin account for us so we can log in and take a look? You can create the account with the following email address:

    Private Snippet

    Just navigate to UsersAdd New in your WordPress admin. Enter siteorigin for the username and Private Snippet for the email address. Make sure you’ve selected Administrator for the role and enabled the Send Password field so we receive the details.

    Once we’re finished taking a look, you can delete this account. We’ll let you know when to do that.

  5. 4 years, 4 months ago jakecroach

    The staging site is still similar enough to still show the problem. I created an admin account for you with that email. And maintenance mode is currently on. To log in, go to flyfortheculture.org/stage/culturelogin

    Let me know if you need anything else. Thanks.

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

    Thanks. The emails should be arriving here in our thread set as private messages that only you and I can read. The emails don’t seem to be arriving. If possible, please, could you set a password for me manually and send it. I’ll delete it when it arrives and set a new password once I’m in.

  7. 4 years, 4 months ago jakecroach

    No worries.

    I didn’t read closely enough on the username. I set username as SOtest not siteorigin. If you need me to make a new one just let me know.

    Password is Private Snippet

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

    Thanks for the update.

    This challenge is similar to the Elementor challenge I mentioned earlier.

    The page was built using Page Builder. If you’d like to migrate away from Page Builder, it would be best to first click the Revert to Editor button to move all the Page Builder code into the Classic Editor. If I activate the Classic Editor plugin and edit the About page, I can see the following:

    https://siteorigin.com/wp-content/uploads/2020/04/about.png

    The page is still a Page Builder page. If I edit the Editor widget and click the Text tab I can see the Block Editor content as follows:

    https://siteorigin.com/wp-content/uploads/2020/04/HTML.png

    To put it all together, the page is a Classic Editor Page Builder page migrated into the Block Editor meaning the Block Editor markup is inserted into the Editor widget in Page Builder but Page Builder isn’t updated as it isn’t managing the page at this stage. To migrate this page you’d need to enable the Classic Editor, edit the page, click the Revert to Editor button and then remove any Page Builder HTML and then deactivate the Classic Editor plugin. OR an easier method would be to activate the Classic Editor plugin, edit the page, edit the Editor widget and copy all of the text and code in the Text tab. Then, click the Rever to Editor button, delete everything in the Text tab and insert the text and code you copied previously, that’ll make sure there isn’t any Page Builder markup remaining.

    I hope that helps, I can answer any follow-ups you may have tomorrow.

  9. 4 years, 4 months ago jakecroach

    Thanks Andrew.

    That did the trick.

    If you don’t mind a quick question so I can make sure I understand: if I have a Page Builder page that I want to edit using Gutenberg, I need to first revert the content to the classic editor and then make the switch? Is there a way for SO widgets to translate directly from a Page Builder layout to a SO block in Gutenberg?

    Thanks for your prompt assistance. I was wrong to be so quick tempered at the offset. Apologies.

  10. 4 years, 4 months ago Andrew Misplon
    Hi, I Work Here

    Super, I’m glad to hear you’re making progress.

    It isn’t possible to automatically migrate a page but you could do it manually by going to LayoutsImport/ExportDownload Layout. With the JSON file on your desktop, rever to the editor and clear the contents from the Text tab. Save and switch over to the Block Editor. Next, insert a SiteOrigin Layout Block and repeat the process, LayoutsImport/Export. Using this process you can move a Page Builder layout from a classic page to a Block Editor page into a SiteOrigin Layout Block. Let me know if you run into any issues with this process.

    You can also use a SiteOrigin Widget Block in Block Editor pages for single widgets.

    I’m glad we could get to the bottom of this complex issue, thanks for hanging in there with us.

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