Home>Support>Page builder issues with WordPress updates, Site Origin Editor won’t load correctly

Page builder issues with WordPress updates, Site Origin Editor won’t load correctly

Hello,

I’m using this theme https://themeforest.net/item/armada-business-and-marketing-wordpress-theme/12761857 which uses the Page Builder by Site Origin plugin (updated now to 2.4.15), in conjunction with a “SiteOrigin Widgets Bundle” plugin (1.7.1) and “AIO Custom Post Plugin” (4.0.5).

I have had issues with updating WordPress (e.g., from 4.6 to 4.6.1), which broke the Page Builder on the homepage and many posts — essentially, what was once in multiple rows with widgets all got condensed into a single row/widget (Site Origin Editor widget), thus, losing all the formatting of the individual rows. I have since reconstructed the homepage and turned off updates: http://psyciq.apa.org/

Now, the newest issue, is that the WYSIWYG editor for Page Builder will not “open/render” at all in the WordPress backend. When creating a new post, I cannot even get the cursor to enter any characters. I can use the regular WP “Text” widget, but not the SiteOrigin Editor widget.

Can you shed any light on this? The template author isn’t much help, and there will be much added to the site soon so I’m hoping to get this resolved.

Also, I already tried deactivating all plugins (issue remains), and switching themes (to the default WP ones), and the issue remains there too.

I am using BlueHost also, not sure if that matters.

It almost seems like the WYSIWYG editor “wants” to load, then shrinks away. I can see the little “resize” arrow on the bottom-right of the editor, but it won’t let me resize either.

Can you please help?

thanks,
Brian

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

  1. 8 years, 7 days ago Alex S
    Hi, I Work Here

    Hi Brian,

    To clarify, are you using the main versions of the plugins or theme forks (a version based on our code but not developed by us)?

    This sounds like it could be a plugin conflict issue as if the editor isn’t working as desired it’s likely being preventing from working by something else interfering.

    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 the above doesn’t help, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.

  2. 8 years, 7 days ago Brian E. Adams

    Hi Alex,

    Thanks so much for getting back to me! This has proven a big problem, and the site is going to start ramping up soon so it’s making me nervous that I can’t update WP anymore, and can’t use the SiteEditor widget anymore either.

    My Page Builder by SiteOrigin plugin is Version 2.4.13 and the SiteOrigin Widgets Bundle plugin is Version 1.6.5. I believe these are the real versions… do those version numbers sound right?

    I actually tried all of those steps — deactivating all plugins and switching the theme, and the problem persisted with not being able to type in the Page Builder editor at all.

    I also tried changing the permissions of the tinymce.php file and directory (something I saw you mentioned in Thread: Page Builder button loads Page Builder but as empty content ), and I was able to get the editor to “open” then, but the text was all white and not visible (only seen if you highlighted it with a mouse).

    I have since been using the “text” widgets instead of the “editor” widget because of this issue.

    I am also wondering if this is all related to the issues I had with PageBuilder and updating WP — where after the update all rows/widgets were condensed into a single instance of the Editor widget (and in a single row)–so, most everything lost it’s styling.

    Also, could this be an issue with BlueHost and security settings on their part (although everything worked “fine” until I first updated WP, and then I started having issues with the condensed into a single row/widget, now this issue where the PageBuilder won’t open and is unusable.)

    Any help is greatly appreciated.

    thanks,
    Brian

  3. 8 years, 6 days ago Alex S
    Hi, I Work Here

    Hi Brian,

    They’re valid version numbers but it’s still possible they’re forks. To clarify, do you see updates for either SiteOrigin Page Builder or the SiteOrigin Widgets Bundle? Both have updates available (2.4.16 and 1.7.1).

    Could you explain what happens before this issue occurs? For example:

    • Enable Page Builder
    • Add and setup image widget
    • Save
    • Reverts to single row

    That would help me with replicating this issue.

    Finally, would it be possible for you to create a temporary admin account for us so we can log in and take a look?

  4. 8 years, 6 days ago Private Message - Alex S Hi, I Work Here

    This is a private message.

  5. 8 years, 6 days ago Private Message - APA Member Services

    This is a private message.

  6. 8 years, 6 days ago Private Message - Brian E. Adams

    This is a private message.

  7. 8 years, 3 days ago Alex S
    Hi, I Work Here

    Hi Brian,

    Sorry for the delay.

    You’re not using a fork. Sorry about that! I always have to ask in instances like this as, regrettably, a lot of theme developers seem to bundle a theme specific version. :( There was a large compatibility issue with an older version of WordPress, we fixed it quite a while before the release but this fix wasn’t implemented in a lot of the forks and thus, you’re unable to update WordPress when using a lot of those forks. This is why I was asked about the fork.

    Now, there aren’t any known incompatibilities with 4.6 and 4.6.1 which is why I’m surprised to hear about your compatibility issues. Would it be possible for me to make a backup of your website for local testing? This will allow me to update WordPress and look into the issue without it affecting your main website.

    I also looked into the editor issue and… well, I’m not too sure why that’s happening. To clarify, I understand the issue but I don’t understand why it’s happening – this is, again, not a widespread issue. The above-mentioned backup will allow me to look into this also as it requires a few setting changes to try and resolve it.

    Oh, and to clarify, 2.4.16 isn’t a must-have update, so I wouldn’t be too concerned about it at the moment.

  8. 8 years, 3 days ago Brian E. Adams

    Hi Alex,

    Thanks again for your help, and in a way, I’m glad you are seeing what I’m seeing.

    Yes, please feel free to make a local copy and test away to try to see what is going on here. And, if you want to update that copy to WP 4.6.1, you can see the other (possibly related) issue with the Page Builder — where all the rows/widgets condense into a single row, happening on the homepage and some posts, but not on pages like the “Careers” page, very strange.

    On the live site, can I go ahead and start making some changes with categories and tags, and some switching around with pages and everything (I’ve put my client on hold while the issues with Page Builder were being explore, but if you are making a local copy for testing, I think whatever comes out of that can translate to the live site). Please let me know if it’s ok for me to start doing some site changes while you are researching this.

    With your backup copy and testing, if you are not experiencing any of these issues, then I’m thinking it may be due to the hosting configurations. But, I’m excited to have your expertise involved with this, as I’m pretty much hitting a brick wall with having theories about what may be wrong, but not being able to narrow it down precisely.

    Please let me know if and how I can help at all.

    Thanks again for all your help!
    -Brian

  9. 8 years, 3 days ago Alex S
    Hi, I Work Here

    Hi Brian,

    Okay – the backup is complete, I’ll running tests now. By all means, continue as you were – hopefully, nothing else comes up.

  10. 8 years, 3 days ago Alex S
    Hi, I Work Here

    Hi Brian,

    :(

    I was able to use the editor and update WordPress without issue. Maybe get in contact with your hosting provider to see if they have any ideas? We haven’t received any reports of any issues with BlueHost but maybe you’re on a plan where they add a couple of mu plugins that could be causing issues.

    If you’re familiar with setting up WordPress locally, I could send you the files for you to try.

  11. 8 years, 3 days ago Brian E. Adams

    Thanks so much, Alex…

    It’s good to know it’s not something in the template and/or the plugin. I’ll contact BlueHost later today and try to get at the bottom of this.

    I really appreciate you taking the time to help me with this!

    I’ll comment back on this ticket with any closure just so you and others know what was the issue with the hosting (if it can be determined, I sure hope so!)

    thanks again,
    Brian

    ps… Ok if I delete away the admin account I had set up for you now?

  12. 8 years, 3 days ago Alex S
    Hi, I Work Here

    Hi Brian,

    Anytime. I look forward to hearing what Bluehost says.

    Delete away! :)

  13. 8 years, 3 days ago Brian E. Adams

    Also, just an fyi, the only file I have in the mu-plugins is sso.php. I’ll start with that once I contact BlueHost…

  14. 8 years, 3 days ago Brian E. Adams

    Hi Alex,

    It turned out to be a conflict with the version of PHP we were running. BlueHost started us off on an older version of PHP, and when we tried to update it, it broke things. So we reverted. Then, when we tried to update WordPress, that broke things, so we reverted. Then, the Page Builder plugin stopped working. What needed to be done was to update everything at the same time, and then the site was working and stable.

    Thanks for your tremendous help and support. I hope running through all of this helps you/someone else. It’s a fantastic plugin! :)

    thanks,
    Brian

  15. 8 years, 3 days ago Alex S
    Hi, I Work Here

    Hi Brian,

    Great to hear that it’s resolved and thank you for letting me know the solution! I’ll be sure to reference it if it comes up again.

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