New WordPress Plugin: Disable Gutenberg

For those still in the dark, WordPress 5.0 will bring HUGE changes to the post editor. Dubbed Gutenberg, the new WP post editor replaces the entire “classic” post editing screen. So as of WordPress 5.0 and beyond, the “Edit Post” screen will be completely replaced by a giant WYSIWYG content builder called “Gutenberg”. So much more is being replaced than just the content editor. The list of things that are replaced by Gutenberg include the RTE/Visual Editor, Plain Text Editor, Custom Fields, and much more.

That means if you are a plugin or theme developer, you may be looking at a LOT of new work required to support Gutenberg, especially if your themes and plugins make use of anything associated with the classic WP post editor (i.e., “Edit Post” screen). And you better know JavaScript. “Deeply”. Or you’re basically in for a battle royale extreme in the coming months. What’s the saying, plan for the worst, hope for the best?

New Plugin: Disable Gutenberg

To help the community with the transition into the Gutenberg (G7G) arena, I’ve written a plugin called Disable Gutenberg. It’s a simple plugin that’s super easy to use, and focused entirely on one thing: disable Gutenberg and restore the Classic Editor.

  • Disable Gutenberg completely (all post types)
  • Disable Gutenberg only on specific post types
  • Disable Gutenberg for specific user roles

So it’s flexible yet simple, and super easy to use. Check out the documentation for more details, and download Disable Gutenberg at the WP Codex.

With Disable Gutenberg, you control when the new editor is rolled out to your clients.

Disable Gutenberg Programmatically

If you are a WordPress developer wanting more information about how to disable Gutenberg via the WP API, check out my DigWP article, How to Disable Gutenberg: Complete Guide. Packed full of juicy infos :)

Download

For more information, list of features, and FREE download, visit Disable Gutenberg at the WP Plugin Directory:

Disable Gutenberg »