Home>Support>Page Builder messed up my editor

Page Builder messed up my editor

By Paddy Landau, 5 years ago. Last reply by Andrew Misplon, 5 years ago.
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].

Yesterday, the last things that I did were to create two new pages and modify the menus. Everything worked well.

This morning, I was advised to install both “Page Builder by SiteOrigin” and “SiteOrigin Widgets Bundle”, which I did. From that point, the bars at the bottom of the editor page (both Pages and Posts) overlay the content. See the screenshot for an example — you can’t see the content apart from most of the title and an image. Scrolling down allows me to see the content lower down, but not the content higher up.

I disabled and uninstalled both “Page Builder by SiteOrigin” and “SiteOrigin Widgets Bundle”, but this hasn’t helped. I changed the theme back to the default Twenty Nineteen, and disabled all of my remaining plugins, but the problem remains.

Might the two plugins have left some code or some database entries that could cause this problem? How can I be sure to completely remove every trace of the two plugins, please?

Thank you

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

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

    Hi Paddy

    Once you’ve deactivated Page Builder and the Widgets Bundle, all scripts and styles from the plugins will be removed/won’t be loaded. To troubleshoot the problem you’re facing try deactivating all plugins at once and switch to a default theme like Twenty Nineteen. The goal is to find a working baseline and then test from there assuming a baseline can be found.

  2. 5 years, 10 months ago Paddy Landau

    Thank you for your reply. I’ll restore an older version and take it from there.

  3. 5 years, 10 months ago Paddy Landau

    I have discovered the problem, and it turned out not to be your plugins.

    It is the latest version of Chrome (version 77).

    It works perfectly in Firefox and in Opera.

    I apologise for the mistake. If you can guide me how to raise this error with the Chrome developers, I’d appreciate it.

    Thank you

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

    Hi Paddy. Glad to hear you’ve made progress. This issue would most likely need to be logged with WordPress. If you’re seeing an issue then there is a good chance it’s already been logged. You can check the issue list here: https://github.com/WordPress/gutenberg/issues.

    If any SiteOrigin questions arise in the future, feel free to open a new thread.

    All the best.

  5. 5 years, 10 months ago Paddy Landau

    Thank you — you are right, it has already been reported.

    https://github.com/WordPress/gutenberg/issues/11060
    https://github.com/WordPress/gutenberg/issues/17406

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

    Thanks for the update. The GitHub issue will be updated as the team attends. Cheers for now :)

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