Back to Community
Home / Community / Plugin → Page builder by siteorigin

Resolving Gutenberg Editor Conflicts with Page Builder by SiteOrigin

13 threads Sep 11, 2025 Plugin → Page builder by siteorigin

Content

Many users of the Page Builder by SiteOrigin plugin have encountered a common issue: the Gutenberg block editor appears to be disabled or becomes inaccessible after installing or updating the plugin. This guide will explain why this happens and provide the most common solutions to restore full editing functionality.

Why Does This Conflict Happen?

Page Builder by SiteOrigin was originally designed to work within the Classic Editor environment. To provide a familiar experience for its users, the plugin's default settings can sometimes prioritize its own editing interface. This is not a bug but a design choice that can lead to confusion, especially for users who wish to use both editors interchangeably or who primarily use Gutenberg. The threads show that this behavior is a frequent point of concern, particularly around updates like version 2.9.6.

Common Solutions to Regain Access to Gutenberg

1. Change the Default Editor Setting

The most straightforward fix is to adjust the plugin's settings. The Page Builder by SiteOrigin team has included an option to control which editor is used by default for new posts and pages.

  • Navigate to Settings > Page Builder in your WordPress dashboard.
  • Locate the setting labeled "Use Classic Editor for new posts" or similar.
  • Ensure this setting is deactivated or unchecked.
  • Save your changes.

This tells WordPress to use the Gutenberg editor as the default for new content.

2. Use the 'Add New' Drop-down Menu

Even if the default is set to the Classic Editor, you can still explicitly create a page using Gutenberg.

  • Go to Pages > All Pages.
  • Click the drop-down arrow next to the "Add New" button.
  • Select "Block Editor" from the options to create a new page with Gutenberg.

3. Disable Page Builder on Specific Post Types

If you only use Page Builder for certain types of content (e.g., pages) but prefer Gutenberg for others (e.g., blog posts), you can disable the plugin for those post types.

  • Navigate to Settings > Page Builder > Post Types.
  • Uncheck the box for any post type where you do not want Page Builder to be active (e.g., 'Posts').
  • Save your changes.

This will ensure the Gutenberg editor loads without conflict for the deselected post types.

4. Utilize the SiteOrigin Blocks within Gutenberg

It's important to note that the two editors are not mutually exclusive. The Page Builder by SiteOrigin team has developed blocks for use within the Gutenberg editor itself.

  • When editing a page in Gutenberg, click the (+) button to add a new block.
  • Search for and add either the "SiteOrigin Layout Block" or a "SiteOrigin Widget Block".
  • These blocks allow you to insert and use Page Builder widgets and layouts directly inside a Gutenberg page.

Conclusion

The apparent disappearance of the Gutenberg editor is a known configuration issue, not a permanent conflict. By adjusting the settings within Page Builder by SiteOrigin, you can seamlessly use both powerful editing tools on your site. The solutions outlined above, derived from community discussions and support threads, provide clear steps to resolve this common point of confusion.

Related Support Threads Support