Classic Editor Addon


GDPR-compliant: does not collect any user data

The free Classic Editor Addon plugin is targeted at everyone who is not yet ready for Gutenberg and/or who does not want to bother clients with Gutenberg. Install it now on sites and by the time WP 5.0 is released, the UX remains the same as you are used to!

The reason we released the “Classic Editor Addon” plugin is because in the beginning the “Classic Editor” plugin did not what it said on the label.

Since version 0.0.4 of the “Classic Editor” plugin, it finally set the default setting to actually using the Classic Editor. It still contains a Settings page though and if the purpose of people is to get the Classic Editor instead of using Gutenberg, then we don’t see the need for such a Settings page.

Also, if we look at developers protecting the sites of their clients with the Classic Editor, they certainly don’t want their clients to accidentally turn off the Classic Editor as Gutenberg adds a lot of undesirable comments, tags and what not to the content.

Therefore we highly recommend installing this “Classic Editor Addon” plugin, which will automatically download the “Classic Editor” plugin to enable easy install. It removes the Settings link from the main Plugins page and removes the plugin’s Settings from the Settings > Writing screen.

We support this plugin exclusively through Github. Therefore, if you have any questions, need help and/or want to make a feature request, please open an issue over at Github. You can also browse through open and closed issues to find what you are looking for and perhaps even help others.

Thanks for your understanding and cooperation.

If you like the Classic Editor Addon plugin, please consider leaving a review. Thanks!

Classic Editor Addon by Pieter Bos and Greg Schoppe.


What is Gutenberg?

Gutenberg is a new editing experience that will drop with WordPress 5.0, whether we like it or not. More information can be found on the Gutenberg FAQ.

Why this addon? Isn’t the purpose of the Classic Editor plugin to disable Gutenberg?

When it was released initially, the “Classic Editor” plugin, by Andrew Ozz, didn’t completely disable Gutenberg without changing settings. Since version 0.0.4 it does, but it still comes with Settings. The “Classic Editor Addon” is a second plugin that makes sure the Settings are gone, so they cannot be accidentally triggered and “bring down the skies”.

How does this compare to other plugins that disable Gutenberg?

Great question! “Classic Editor” is the official plugin for removing Gutenberg, and the install count is apparently being used as a metric to gauge success of the Gutenberg project. So, although other plugins exist to force-disable Gutenberg, using them doesn’t properly notify the WP Core team of the number of issues users are having, that is why “Classic Editor Addon” doesn’t disable Gutenberg itself, it just removes the Settings page of the “Classic Editor” plugin, making it easier to mass-install classic editor.

The plugin doesn’t do anything!

Is Gutenberg active on the site and do you have the Classic Editor plugin installed? Those two are requirements for this addon plugin to do anything. If you have and the plugin still doesn’t do anything, then please open a support ticket.

I have an issue with this plugin, where can I get support?

Please open an issue on Github


Neat way of preserving my sanity!

Thanks for this – very much appreciated.

I added this to all my clients’ sites yesterday after one of them responded to the 4.9.8. Gutenberg nag and found themselves completely bamboozled by what confronted them.

They are safely back on the Classic Editor now and I’ve added this Addon to all my clients’ sites to avoid them facing the same problem.

Thank a lot!

Yesterday I sent out to all my clients a warning “Do not try use Gutenberg!” but it was too late 🙂 One of the clients replied that he had already installed Gutenberg and published one article. It was terrible, he said. Today I installed your plugin on 15 client sites and updated the WordPress. Everything went good, everything works. Great job, guys!


Nothing else to say. It will greatly help the non-passage to Gutenberg.

WordPress Apartheid

What Automattic going to do is a deliberate act of prevarication. I don’t think I can stand it. I love the plugin if it can save us from Gutenberg, but I am afraid it won’t.

The “classic editor plugin” is going to be like the South African Apartheid, or the Indian Reservations for the Native American Tribes. I don’t think free people should accept it.

Read all 10 reviews

Contributors & Developers

“Classic Editor Addon” is open source software. The following people have contributed to this plugin.


“Classic Editor Addon” has been translated into 4 locales. Thank you to the translators for their contributions.

Translate “Classic Editor Addon” into your language.

Interested in development?

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



  • October 25, 2018
  • fix typo which addresses issue #3


  • August 28, 2018
  • remove functions that have become redundant since 0.0.4 release of Classic Editor plugin
  • rewrite readme files


  • July 16, 2018
  • add WP Dependency Installer to facilitate with installing and activating Classic Editor plugin (changed color of admin notice to blue)
  • adjust minimum PHP version (to 5.3) due to addition of WP Dependency Installer


  • July 12, 2018
  • fix issue #2
  • adjust readme text and FAQs


  • July 8, 2018
  • release of plugin on WordPress Plugin Directory, ready for the world 🙂


  • early July, 2018
  • more feature/function/code improvements by both Pieter & Greg