Understanding Disable Gutenberg Plugin Compatibility

Many WordPress users rely on the Disable Gutenberg plugin to maintain the classic editing experience. A common question that arises is about the plugin's compatibility with various WordPress setups, including older versions, multisite installations, and other popular plugins.

Based on community discussions and user reports, here's a clear breakdown of what works and what doesn't.

WordPress Version Compatibility

The Disable Gutenberg plugin has a minimum requirement of WordPress 4.9 or newer. If your site is running on WordPress 4.6 or 4.7, this plugin will not be compatible.

Why this happens: The plugin is built using code structures that are only supported in WordPress 4.9 and above.

The solution: For sites on older versions (pre-4.9), Gutenberg is not part of the core software. You can simply ensure that the standalone Gutenberg plugin is not installed or is deactivated. The classic editor will be the default experience without needing an additional plugin to disable Gutenberg.

Multisite (WPMS) Compatibility

A user inquired about using Disable Gutenberg on a WordPress Multisite network.

The current status: The plugin's developers have stated that it is not officially developed or tested on Multisite installations.

Why this matters: Without official testing, there is no guarantee of flawless performance across a network. However, anecdotal evidence from the community suggests that it may still function. There have been no widespread reports of it failing on Multisite, but users should proceed with caution and test on a development site first.

Compatibility with SEO Plugins

Questions often arise about potential conflicts with major SEO plugins, specifically Yoast SEO and All In One SEO Pack.

The verdict: Community testing has shown that the Disable Gutenberg plugin works correctly with both Yoast SEO and the All In One SEO Pack plugin. Users have confirmed that they can run these popular SEO solutions alongside Disable Gutenberg without experiencing conflicts.

If you are testing a new configuration, it is always a best practice to do so on a staging site first to ensure everything works as expected for your specific setup.

What Happens After WordPress 5.0?

Since Gutenberg was merged into WordPress core in version 5.0, the Disable Gutenberg plugin remains relevant for those who wish to opt out of the block editor. The plugin will continue to disable Gutenberg and remove related admin notices for as long as it is active. It is safe to keep installed on sites running WordPress 5.0 and beyond.