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 the new editing experience that has been introduced in WordPress 5.0. Install it now on sites and the UX remains the same as you are used to!

What’s New:
Sites running WooCommerce get another style added to the <head> section of the site. With the Classic Editor Addon installed that call is obviously redundant. With version 2.5.0 we introduce a condition that checks for WooCommerce and if active it removes that call. Win!

Please pay attention that the minimum PHP version to use our plugin is 5.4.

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 the new block editor, 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 the new block editor 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 install the “Classic Editor” plugin and remove its settings.

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 here. 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 this new block editor that ships with WordPress 5.0?

The release of WordPress 5.0 comes with a replacement of the TinyMCE editor you have gotten used to. Some find it an improvement, others don’t. More information can be found on the WP 5.0 release post.

Why this addon? Isn’t the purpose of the Classic Editor plugin to disable the new block editor?

When it was released initially, the “Classic Editor” plugin, by Andrew Ozz and other “WordPress Contributors”, didn’t completely disable the new block editor 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 the new block editor?

Great question! “Classic Editor” is the official plugin for removing the new block editor, and the install count is apparently being used as a metric to gauge success of the project. So, although other plugins exist to force-disable the new block editor, 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 the new block editor itself, it just removes the Settings page of the “Classic Editor” plugin, making it easier to mass-install the “Classic Editor” plugin.

The plugin doesn’t do anything!

Has the site been updated to WordPress 5.0 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


19 de Enero de 2019
I want to say thank you so much for creating this plugin. I actually felt like I was loosing my motivation creating new post because of this new classic editor that had taken over my pages and post after updating to the new WordPress 5.0. It was fancy and complicated and wasn't allowing me to apply my custom affiliate links which was very discouraging. I'm now motivated to start working on my first new article for 2019 my heart is smiling and I'm overjoyed. Thank You A Million
17 de Enero de 2019
The "Classic Editor" is a nice try, but it kind-a squeezes the "old" editor into the Gutenberg view. Not only that, it doesn't even respect the CSS that I used in the "old" editor. This magnificent addon does exactly what is missing! The old editor is back the way it actually used to be! Thanks guys for creating this addon - I'm not a Gutenberg fan, and am not looking forward to "fixing" what wasn't broken to begin with. You guys saved me a lot of work!! I highly recommend this addon for the "Classic Editor" if you want to really see the old editor.
10 de Enero de 2019
Thanks for this added security against Gutenberg! Everything that can be done to protect our websites from Gutenberg as it is right now must be done! 🙂
21 de Diciembre de 2018
Then I stopped and asked myself, "I cannot be the only one who despises the new editor!" I actually spent several days to look at switching to a new CMS... Thank You! It does work perfectly for my needs...
14 de Diciembre de 2018
The Classic Editor plugin is helpful, but this plugin makes it better. This plugin hides Gutenberg options and prevents users from deactivating Classic Editor plugin to use the Gutenberg editor. Classic Editor Addon provides a safety net: it protects your site's content from "mystery meat" blocks.
Leer los 22 comentarios

Colaboradores & Desarrolladores

“Classic Editor Addon” es software de código abierto. Las siguientes personas han contribuido a este plugin.


“Classic Editor Addon” ha sido traducido en 7 idiomas. Gracias a los traductores por sus contribuciones.

Traduce & #8220;Classic Editor Addon” a tu idioma.

¿interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN , o suscríbete al log de desarrollo por RSS .

Historial de cambios


  • October 11, 2019
  • add function that removes the 1 block editor style call from the <head> section of your site when WooCommerce is running


  • January 22, 2019
  • add function that removes the 2 block editor style calls from the <head> section of your site


  • December 17, 2018
  • increase minimum PHP version to 5.4 due to introduction new shorthand syntax of WP Dependency Installer update in 2.3.0


  • December 14, 2018
  • version update WP Dependency Installer
  • add parameter "optional": false as a workaround to fix issue #4


  • December 12, 2018
  • rewrite of function that removes settings of the Classic Editor plugin


  • 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