Disable Gutenberg

Description

This plugin disables the new Gutenberg Editor (aka Block Editor) and replaces it with the Classic Editor. You can disable Gutenberg completely, or selectively disable for posts, pages, roles, post types, and theme templates. Plus you can hide the Gutenberg nag, menu item, and more!

The all-in-one, COMPLETE solution for handling Gutenberg.
Hide ALL traces of Gutenberg and replace with the Classic Editor.
Restores the original Edit Post screen (TinyMCE, meta boxes, et al).

The Disable Gutenberg plugin restores the classic (original) WordPress editor and the “Edit Post” screen. So you can continue using plugins and theme functions that extend the Classic Editor. Supports awesome features like Meta Boxes, Quicktags, Custom Fields, and everything else the Classic Editor can do.

Options

  • Disable Gutenberg completely (all post types)
  • Disable Gutenberg for any post type
  • Disable Gutenberg for any user role
  • NEW: Disable Gutenberg for any theme template
  • NEW: Disable Gutenberg for any post/page IDs
  • Disable Gutenberg admin notice (nag)
  • Option to hide the plugin menu item
  • Option to hide the Gutenberg plugin menu item (settings link)
  • NEW! Adds WP menu item: “Add New (Classic)”
  • NEW! Adds post link to “Edit (Classic)”

Works same way as Classic Editor plugin, but can do a LOT more!
Lightweight and super fast, built with the WP API 🙂

Fully configurable, enable or disable Gutenberg and restore the Classic Editor wherever is necessary.

Automatically replaces Gutenberg with the Classic Editor.

Features

  • Super simple
  • Clean, secure code
  • Built with the WordPress API
  • Lightweight, fast and flexible
  • Regularly updated and “future proof”
  • Works great with other WordPress plugins
  • Plugin options configurable via settings screen
  • Focused on flexibility, performance, and security
  • One-click restore plugin default options
  • Translation ready

Plus, unlike similar plugins, Disable Gutenberg does NOT add extra Gutenberg options to the WordPress “Writing” settings.

Super light & fast plugin, super easy on server resources!

Why?

Gutenberg is a useful editor but sometimes you want to disable it for specific posts, pages, user roles, post types, or theme templates. Disable Gutenberg enables you to disable Gutenberg and replace it with the Classic Editor wherever you want. For example, lots of WordPress users already enjoy robust page-building functionality via one of the many great plugins like Composer or Elementor. So many options, no need to feel “locked in” to using Gutenberg!

The Disable Gutenberg plugin is targeted at everyone who is not ready for the major changes brought by Gutenberg. Install Disable Gutenberg NOW to be ready for when Gutenberg is finally merged into core and released to the public (likely in WP 5.0). That way, your users and clients will experience the same awesome UX as before 😉

GDPR

This plugin does not collect any user data. So it does not do anything to make your site less compliant with GDPR. I have done my best to ensure that this plugin is 100% GDPR compliant, but I’m not a lawyer so can’t guarantee anything. To determine if your site is GDPR compliant, please consult an attorney.

If you like this plugin, please give it a 5-star rating to encourage future development.

Support development of this plugin

I develop and maintain this free plugin with love for the WordPress community. To show support, you can make a donation or purchase one of my books:

And/or purchase one of my premium WordPress plugins:

Links, tweets and likes also appreciated. Thanks! 🙂

Screenshots

  • Plugin Settings screen (showing default options)
  • Plugin Settings screen (showing expanded options)

Installation

Installing the plugin

  1. Upload the plugin to your blog and activate
  2. Configure the plugin settings as desired
  3. Enable theme switcher via settings or shortcode

More info on installing WP plugins

Important

Do not use Disable Gutenberg with other plugins (like the Classic Editor plugin) that also disable or replace Gutenberg. Why? Because it may cause loading of redundant scripts, which may in turn lead to unexpected/untested results.

Hide Menu Option

Disable Gutenberg provides a setting to disable the plugin’s menu item. This is useful if you don’t want your clients to get curious and start fiddling around.

If you enable the option to hide the plugin’s menu item, you will need to access the plugin settings page directly. It is located at:

/wp-admin/options-general.php?page=disable-gutenberg

So if WordPress is installed at this URL:

https://example.com/

..then you would access the plugin settings at:

https://example.com/wp-admin/options-general.php?page=disable-gutenberg

Or, if WordPress is installed in a subdirectory, for example:

https://example.com/wordpress/

..then you would access the plugin settings at:

https://example.com/wordpress/wp-admin/options-general.php?page=disable-gutenberg

So if you hide the plugin’s menu item, you always can access the settings directly.

Uninstalling

This plugin cleans up after itself. All plugin settings will be removed from your database when the plugin is uninstalled via the Plugins screen.

FAQ

Will this work without Gutenberg?

Yes. When Gutenberg is active, the plugin disables it (depending on your selected options) and replaces with the Classic Editor. Otherwise, if Gutenberg is not active, the plugin does nothing. So it’s totally fine to install before Gutenberg is added to WP core, so it will be ready when the time comes.

What’s the difference between Classic Editor plugin?

Classic Editor plugin enables you to disable Gutenberg across the board, and replace it with the Classic Editor. The Disable Gutenberg plugin does the exact same thing, in the exact same way, BUT it also provides more granular control over when and where Gutenberg is replaced with the Classic Editor. Disable Gutenberg plugin makes it easy to replace Gutenberg everywhere, OR you can choose to replace only for specific post types, user roles, post IDs, theme template, and more. Check out the list of features and compare them to the alternatives. It’s not even close! 😉

Bottom line: both Disable Gutenberg and Classic Editor plugins are lightweight and enable you to replace Gutenberg with the Classic Editor for the entire site. The difference is that Disable Gutenberg also gives you advanced configuration options including menu hiding and more.

Why does Classic Editor plugin have way more users?

Because it is being promoted by the Gutenberg developers and the “official” plugin for replacing Gutenberg. That’s fine, but understand that Disable Gutenberg functions the same way AND provides way more features and settings. FWIW, I use Disable Gutenberg on my sites Perishable Press, DigWP.com, Plugin Planet, and many others. 100% solid.

Template exclusions not working?

In order for template exclusions to work, the template must be registered with the page itself. The only way to do this is via the “Edit Page” screen, in the “Page Attributes” meta box. There you will find an option to set the page template. Remember to save your changes.

After assigning some templates, they will be recognized by Disable Gutenberg. So to disable Gutenberg on any registered template, you can add them via the plugin setting, “Disable for Templates”. Important: the template name must be written as page-custom.php, only using the actual file name of whichever template you want to use.

Got a question?

Send any questions or feedback via my contact form

Reviews

THANK YOU from a WP Developer

We shouldn’t even need this plugin, but I’m grateful you have it in place so I can protect the 17 highly customized WordPress sites I’ve created from the Gutenberg debacle.

Thank God

The perfect plugin to remove a complicated authoring experience.

Read all 45 reviews

Contributors & Developers

“Disable Gutenberg” is open source software. The following people have contributed to this plugin.

Contributors

“Disable Gutenberg” has been translated into 3 locales. Thank you to the translators for their contributions.

Translate “Disable Gutenberg” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.4 (2018/11/09)

  • Refactored for changes in Gutenberg plugin
  • Checks for Classic Editor plugin is active
  • Restores “Edit Classic” feature for WP 5.0+
  • Further tests on WP 4.9.8 and 5.0 beta

1.3.1 (2018/10/29)

  • Rolls back new “Edit Classic” feature introduced in 1.3
  • Further tests on WP 5.0 beta

1.3 (2018/10/27)

  • Refactored for WordPress 5.0 (Gutenberg merged into core)
  • Ensures functionality on pre-5.0 WP versions
  • Adds WP menu item: “Add New (Classic)”
  • Adds post link to “Edit (Classic)”
  • Tests on WordPress 5.0 (beta)

1.2 (2018/08/14)

  • Adds rel="noopener noreferrer" to all blank-target links
  • Adds options to disable Gutenberg for specific post templates and post IDs
  • Adds option to hide/remove the Gutenberg plugin menu item
  • Adds Classic Editor replacement for WP 5.0 (in progress)
  • Fixes object-related PHP warning in enqueue script
  • Updates GDPR blurb and donate link
  • Tweaks CSS on plugin settings page
  • Adds “rate this” link to settings page
  • Generates default translation template
  • Further tests on WP versions 4.9 and 5.0 (alpha)

1.1 (2018/05/06)

  • Removes unused .otf font file
  • Adds option to disable “Try Gutenberg” nag (admin notice)
  • Adds option to hide the plugin’s menu item
  • Further testing on WP 5.0 (alpha)

1.0 (2018/04/16)

  • Initial release