Home>Support>Conflict with Gutenberg

Conflict with Gutenberg

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].

Hi, there appears to be a conflict with Site Origin Page Builder and Gutenberg. When I first installed Page Builder I set it to allow users to switch between Editors. This option showed up within the page under page attributes. WordPress is now up to date with version 5.2.1 and this option has disappeared. I can set the default editor to Gutenberg for my user profile in WordPress settings so when I create a new page it opens in Gutenberg Editor …but I can’t switch back to Site Origin Page Builder. Also, in the list of pages, when I hover over an existing page and click edit with Block Editor, it doesn’t work. The page opens with Site Origin Page Builder and Classic Editor options only.

I deactivated all plugins on the website and checked in an existing page and the switch editors option was there. I reactivated the plugins one at a time and each time I activated one I checked an existing page to see if the option to switch editors was still there. It was until I reactivated Page Builder by SiteOrigin and then this option to switch Editors disappeared.

Have anyone experience this problem, I would be grateful if I could get some advice on how to solve this? Is there a known conflict with Gutenberg, SiteOrigin Page Builder & the latest WordPress April 2019 update?

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. 6 years, 1 month ago Andrew Misplon
    Hi, I Work Here

    Hi Karen

    Thanks for reaching out.

    The challenge relates to compatibility with the Classic Editor plugin. “Default editor for all users” and “Allow users to switch editors” are writing settings provided by the Classic Editor plugin. The issue has been logged here: https://github.com/siteorigin/siteorigin-panels/issues/673. The scope of the issue isn’t yet known but we’ll attend as soon as possible.

    If you deactivate the Classic Editor plugin, you could at least choose to create Classic or Block Editor pages from PagesAll Pages, click the drop-down arrow next to the Add New button at the top of the page, you can choose between Page Builder Page (Classic) or a Block Editor page.

  2. 6 years, 1 month ago karenw

    …so is there no way to have the classic editor plugin installed & the option to switch between them. I have an editor on my site that is only familiar with the classic editor & not page builder or block editor.

    Karen

  3. 6 years, 1 month ago Andrew Misplon
    Hi, I Work Here

    Hi Karen

    The switching functionality provided by the Classic Editor isn’t currently functioning when Page Builder is activated. The issue mentioned above, #673 is the bug report for that, as we attend, any notes or challenges will be documented there. With the Classic Editor activated, your editor would be able to work in the Classic Editor interface, the issue would then be that none of the Block Editor pages would be editable in the Block Editor interface.

    With the Classic Editor plugin deactivated, you can create either Block or Page Builder (Classic) pages from PagesAll Pages, click the drop-down arrow next to Add New and choose. The issue there is that if a Page Builder (Classic) page is created and no Page Builder content is added, the page will revert to the Block Editor on save.

    I’m working to have this attended to as soon as possible.

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

    A quick update. If you deactivate the “Allow users to switch editors” setting at SettingsWriting, Block Editor pages will remain in the Block Editor and not revert to Classic after saving and navigating away from the page. We’ll continue to work the issue, hopefully to a resolution soon.

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