Support » Plugin: Page Builder by SiteOrigin » Conflicts with Classic Editor plugin

  • Resolved sankari



    Thank you for providing and maintaining this free plugin.

    Page Builder by SiteOrigin seems to be conflicting with the popular Classic Editor plugin (

    * WordPress 5.2.1
    * Page Builder by SiteOrigin 2.10.5
    * Classic Editor Plugin 1.5

    Classic Editor plugin options:
    * Default editor for all users: Block editor
    * Allow users to change the editor: Yes

    WordPress user profile settings:
    * Standard editor: Block editor

    If both plugins are active I noticed these issues happening:

    1) Clicking the “Edit (Block Editor)” link for posts or pages launches the Classic Editor (instead of the Block Editor showing a Classic Block).

    2) Creating a new post by specifically using the Block Editor (Posts > Create > Block Editor) launches the Block Editor. After saving the post as draft it says on the post list that the post was last edited using “Classic Editor”.

    3) Posts that had been created using the Classic Editor cannot be edited using the Block Editor.

    4) By editing a post the meta box to switch the editor is missing.

    See my post at They advised me to contact your support.

    Thank you for looking into this!

    • This topic was modified 1 year, 9 months ago by sankari.
    • This topic was modified 1 year, 9 months ago by sankari.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Andrew Misplon


    Hi, thanks for reaching out and for your kind words.

    I’ll log issue reports for these challenges.

    For the moment, you could consider the following:

    1. Deactivate the Classic Editor plugin.
    2. At Settings > Page Builder > General you can use Use Classic Editor for new posts to decide whether new posts should default to Classic or not.
    3. From Pages > All Pages, note the drop-down arrow next to the Add New button. If you click that button you can choose between creating a Page Builder page (Classic) or a Block Editor page. Note that if you create a new Classic page and don’t add any Page Builder data, it’ll revert to Block Editor.

    From the testing I’ve done now, the above is more functional that leaving the Classic Editor enabled.

    We’ll do our best to get these challenges resolved ASAP.

    Plugin Author Andrew Misplon


    Thread Starter sankari


    Hello @misplon

    Thank you very much for your prompt reply and for logging these issues. Your advice in point 2 is very helpful as I was not aware of that option.

    Have a peaceful day!

    Plugin Author Andrew Misplon


    For sure, thanks for your understanding and feedback. I’ll update you as soon as I have any news to report.

    Plugin Author Andrew Misplon


    Hi again. A quick update to let you know that the upcoming release of Page Builder resolves most of the challenges we’ve discussed. Please, note that switching Classic pages with Page Builder data in them isn’t currently possible. If a Classic page doesn’t have Page Builder data in it then it can be switched to a Block Editor page. The reason for this is that we haven’t been able to reliably offer data migration between the classic Page Builder interface and our SiteOrigin Layout block in the Block Editor. The other features of the Classic Editor plugin should now be functioning normally, they are in our testing.

    Thread Starter sankari


    Hello Andrew

    Thank you for the good news.

    For Classic pages with Page Builder data in it do you consider prompting users with a notice that switching isn’t possible if they try to? I imagine that would be helpful for users and save you some support effort in the future.

    • This reply was modified 1 year, 8 months ago by sankari.
    Plugin Author Andrew Misplon


    Thanks for your feedback, agreed. I’ll raise this with the team.

    If any SiteOrigin questions arise in the future, please let us know.

    Cheers for now 🙂

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Conflicts with Classic Editor plugin’ is closed to new replies.