Download

Disable Gutenberg

By Jeff Starr

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, etc.).

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.

Does not “expire” in 2022! 🙂

Easy to Use

Just activate and done! The default plugin settings are configured to hide all traces of the Gutenberg Block Editor, and fully restore the original Classic Editor. Further options for customizing when/where Gutenberg is enabled are available in the plugin settings.

Options

  • Disable Gutenberg completely (all post types)
  • Disable Gutenberg for any post type
  • Disable Gutenberg for any user role
  • Disable Gutenberg for any theme template
  • 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)
  • Adds “Classic Editor” link to each post on the Posts screen
  • Adds item to the WP sidebar menu: “Add New (Classic)”
  • NEW! Option to enable Custom Fields Meta Box for ACF
  • NEW! Choose which editor to use for each post
  • NEW! Whitelist any post title, slug, or ID
  • NEW! Option to disables frontend Gutenberg stylesheet

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

Disable Gutenberg is developed by Jeff Starr, 13-year WordPress developer, book author, and support guru.

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 😉

Privacy

This plugin does not collect or store any user data. It does not set any cookies, and it does not connect to any third-party locations. Thus, this plugin does not affect user privacy in any way.

If you like this plugin, please give it a 5-star rating, thank you!

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

Settings

Out of the box, Disable Gutenberg makes your WordPress 100% Gutenberg-free. If you visit the settings page, you will see that the “Complete Disable” option is enabled, and so is the “Disable Nag” option. This is all that is required to disable Gutenberg (and the nag) sitewide.

Now, if you want to customize things and, say, only disable Gutenberg on specific post types, you can uncheck that first “Complete Disable” option. When you uncheck the box, more options will be displayed. So you can choose exactly where Gutenberg should be disabled.

Whitelist

In some cases, you may want to disable Gutenberg everywhere, but enable only on certain posts. To do this, set the “Complete Disable” option to enabled. Then visit the “Whitelist” settings to specify which posts always should open in the Block Editor.

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.

More Tools

Here is a description of the tools available by clicking the “More Tools” link.

  • Disable Nag – Disables “Try Gutenberg” nag
  • Enable Frontend – Enables the frontend Gutenberg stylesheet
  • Whitelist Options – Displays the Whitelist settings
  • Plugin Menu Item – Hides the Disable Gutenberg menu item
  • Gutenberg Menu Item – Hides the Gutenberg plugin menu item (for WP less than 5.0)
  • Display Edit Links – Displays “Add New (Classic)” menu links and Classic/Block edit links
  • ACF Support – Enables the Custom Fields Meta Box (ACF plugin disables by default)
  • Reset Options – Restores the default plugin options

If there are any questions about these items or anything else, feel free to contact me directly or post in the WP Support Forums.

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.

Going Further

For developers wanting to customize further, check out:

Show Support

I strive to make this free plugin the very best possible. To show support, please take a moment to leave a 5-star review at WordPress.org. Your generous feedback helps to further growth and development of Disable Gutenberg. Thank you!

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.

Can I activate Disable Gutenberg without Gutenberg?

Yes, you can install and activate Disable Gutenberg on any supported WordPress version (see Docs/readme.txt for details). If installed on WP versions less than 5.0 without the Gutenberg plugin active, the Disable Gutenberg plugin simply won’t do anything (but you can still configure settings, etc.).

Can I use Disable Gutenberg and Classic Editor at the same time?

Yes, if both plugins are active at the same time, Disable Gutenberg gives priority to Classic Editor plugin. So if you want to use Disable Gutenberg, deactivate the Classic Editor plugin (you do not have to remove it, just deactivate via the Plugins screen).

Classic Editor expires in 2022, what about Disable Gutenberg?

I can’t make any promises, but I intend to develop with WordPress for the long-haul. Who knows what the future holds, but the plan is to keep Disable Gutenberg going for many years to come. Why? Because the original RTE/Visual Editor is awesome. I strongly feel it’s one of the many reasons why WordPress has enjoyed its great success. I’ve been using the original/classic editor for over 10 years now and it’s always been 100% smooth experience. I’ve tried Gutenberg, and yes it is much better now than in previous versions, but for me it’s just not as comfortable or streamlined as the classic editor. So yeah, will do everything possible to keep Disable Gutenberg (and the Classic Editor) going well beyond 2022.

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”. Examples:

  • Template name is page-custom.php, located in the root theme directory: enter page-custom.php in the Template Exclusion setting
  • Template name is page-custom.php, located in a subdirectory named templates: enter templates/page-custom.php
The shortcut links are mixed up?

In previous versions the default was to show the Gutenberg Editor links. In 1.5.2, the default is to hide the extra editor links. So what I’m guessing happened in this case is that you had a previous version of DG and changed some settings. When you did that, it set the “show edit links” option to the then default, which is enabled. So now that you have upgraded, that saved “enabled” option still applies. Now to fix, you can do one of two things:

  • Visit the More Tools and disable the option to “Display Edit Links”
  • Or simply click to Restore the default plugin settings

Either route will get you there.

Got a question?

Send any questions or feedback via my contact form

Reviews

Life-saver!

May 25, 2020
After installing WP 5.4.1, all of a sudden, the editor went into blank page of death mode. That was for every site in the multisite installation, even those with all default settings and no plugins installed. After wasting time with the "solutions" proposed by the WP moderators (you know, all that shit they suggest based on the assumption that their product is perfect and therefore you suck), i came across a post suggesting to disable the new amazing Gutenberg (Block) editor. Installed this plugin and everything started to work again. Life-saver!

Can’t live without it!

May 15, 2020
Two days ago I surrendered and disabled "Disable Gutenberg" - - - only for an hour-and-half. I thought I should give Gutenberg another chance - specially since I'm designing a new front page for my blog and don't want to use a page builder either... Well, as mentioned: I didn't last for 2 hours! "Disable Gutenberg" is back on, the page is almost done - much faster w/o Schlechtenberg (which deleted several of my inline styles - just because it could!). I hope Disable Gutenberg will be with us for years to come! Otherwise I will have to look for a new CMS (maybe Ghost?). ps: Schlechtenberg is my nickname for the new editor: gut is good in German, schlecht is bad

At last,

May 12, 2020
At last!. I was confused with all those editors. I prefer my simple one
Read all 484 reviews

Contributors & Developers

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

Contributors

“Disable Gutenberg” has been translated into 12 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

Thank you to everyone for using Disable Gutenberg and for all the awesome 5-star reviews!

If you have any feedback or suggestions to make this plugin the absolute best it can be, and/or would like to help with development, please reach me via my contact form at Perishable Press.

2.1 (2020/03/13)

  • Bumps version number
  • Tests on WordPress 5.4

2.0 (2019/10/26)

  • Updates styles for plugin settings page
  • Fixes bug with front-end script loading
  • Fixes bug with disable for page templates
  • Generates new default translation template
  • Tests on WordPress 5.3

1.9 (2019/09/02)

  • Updates check for existing Gutenberg plugin
  • Improves logic of disable_gutenberg_remove()
  • Updates hooks in disable_gutenberg_hooks()
  • Updates some links to https
  • Tests on WordPress 5.3 (alpha)

1.8.1 (2019/04/29)

  • Fixes PHP Notice: “Trying to get property ID of non-object”
  • Tests on WordPress 5.2

1.8 (2019/04/28)

  • Bumps minimum PHP version to 5.6.20
  • Fixes bug with block stylesheets and whitelisted posts
  • Updates default translation template
  • Tests on WordPress 5.2

1.7 (2019/03/06)

  • Fixes bug with empty titles reverting to Gutenberg
  • Removes requirement for custom fields for post types
  • Resolves error when using as mu-plugin (thanks Dave Lavoie)
  • Adds enable/disable support for wp-block-library-theme
  • Tweaks plugin settings screen UI
  • Generates new default translation template
  • Tests on WordPress 5.1 and 5.2 (alpha)

1.6 (2019/02/02)

  • Just a version bump for compat with WP 5.1
  • Full update coming soon 🙂

1.5.2 (2018/12/11)

  • Changes default option for the menu and edit links
  • Adds option to disable frontend Gutenberg styles
  • Updates default translation template

1.5.1 (2018/12/10)

  • Fixes possible false negative with whitelist settings
  • Tests on WordPress 5.0

1.5 (2018/12/10)

  • Increases minimum required WP version to 4.9
  • Increases minimum required PHP version to 5.2.4
  • Adds whitelist options for post IDs, slugs, titles
  • Adds filter hook disable_gutenberg_submenu_types
  • Adds option to enable Custom Fields Meta Box for ACF
  • Adds “Block Editor” link to each post on Posts screen
  • Adds option to disable “Add New (Classic)” menu link and “Classic Editor” edit link
  • Improves Privacy Policy admin notice (thanks to Classic Editor plugin for the idea)
  • Hides “Edit (Classic)” on Posts screen for posts where Gutenberg is disabled
  • Removes $current_screen global where not needed
  • Improves logic of page_row_actions
  • Removes disable_gutenberg_replace()
  • Improves logic in classic-editor.php
  • Removes /classic-editor/ library
  • Refactors settings JavaScript file
  • Hides the “More Tools” options by default
  • Fine-tunes verbiage on plugin settings page
  • Adds homepage link to Plugins screen
  • Updates default translation template
  • Tests on WordPress 5.0

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

Meta

Ratings

See all
Log in to submit a review.

Contributors

Support

Issues resolved in last two months:

4 out of 4

View support forum

Donate

Would you like to support the advancement of this plugin?

Donate to this plugin