Description
Classic Editor is an official plugin maintained by the WordPress team that restores the previous (“classic”) WordPress editor and the “Edit Post” screen. It makes it possible to use plugins that extend that screen, add old-style meta boxes, or otherwise depend on the previous editor.
Classic Editor is an official WordPress plugin, and will be fully supported and maintained until at least 2022, or as long as is necessary.
At a glance, this plugin adds the following:
- Administrators can select the default editor for all users.
- Administrators can allow users to change their default editor.
- When allowed, the users can choose which editor to use for each post.
- Each post opens in the last editor used regardless of who edited it last. This is important for maintaining a consistent experience when editing content.
In addition, the Classic Editor plugin includes several filters that let other plugins control the settings, and the editor choice per post and per post type.
By default, this plugin hides all functionality available in the new Block Editor (“Gutenberg”).
Screenshots

Admin settings on the Settings -> Writing screen. 
User settings on the Profile screen. Visible when the users are allowed to switch editors. 
"Action links" to choose alternative editor. Visible when the users are allowed to switch editors. 
Link to switch to the Block Editor while editing a post in the Classic Editor. Visible when the users are allowed to switch editors. 
Link to switch to the Classic Editor while editing a post in the Block Editor. Visible when the users are allowed to switch editors. 
Network setting to allow site admins to change the default options.
Reviews
Classic Editor is making WP great again 😉
Thanks, Classic Editor is simple and easy to use.
BR Pete,
Mandatory after Gutenberg
Using Divi most of the time, I don’t like at all using Gutenberg as it is right now.
So there is no other choice than to set up Classic editor.
I would have prefered Gutenberg as a plugin with the free choice to implement it or not.
PRAISE THE LORD!!!!
The first time I used Gutenberg, it took me over two hours to do a very simple blog post about my dog. It was so frustrating I ended up doing the ugly face ‘cranky cry’.
I also screamed “where’s the @#*&% code???!!!” so loud (multiple times!) I’m pretty sure I woke my neighbors up.
In short: I HATE GUTENBERG!!!
I’ve been building webpages and websites since hand-html coding was our only option, so I’m no beginner. I’ve also been using page builders like SiteOrigin and WPBakery Page Builder for years, so I know my way around drag and drop.
Gutenberg is absolutely awful, and certainly no competition for those plugins. It isn’t even in the same hemisphere. Or on the same planet. Or universe. I don’t know where it is, but it won’t be anywhere near my blog posts and pages again.
Thank you SOOOOOO much for this plugin!!
Thank you for bringing back the classic editor!
Thank you for bringing back the classic editor!
We were dissapointed after we discovered how strange, weird and time consuming Guttenberg was. Thank you for this plugin.
Johannes Gutenberg rolled over in his grave
I was shocked when i saw this new block editor. I dont know if i can write it here and im sorry but i think its real shit. I use wordpress 10 years and always was happy and satisfied with this, never had any wish to change to somethng else. I just hope u will continue to support this plugin. thank you for everything u do but sometimes u can make mistakes too and this Gutenberg is mistake. I think real Johannes Gutenberg rolled over in his grave when he saw what u have done))
Gutenburg
Something seriously wrong here with Gutenburg when there are over 2 million downloads of the classic editor, which I have to say has been a godsend. Even the other *classic editor” has over 90000 downloads. WordPress needs to take note and make Gutenburg an option because if they don’t I can see users moving on in their droves!
Contributors & Developers
“Classic Editor” is open source software. The following people have contributed to this plugin.
Contributors“Classic Editor” has been translated into 43 locales. Thank you to the translators for their contributions.
Translate “Classic Editor” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.3
- Fixed removal of the “Try Gutenberg” dashboard widget.
- Fixed condition for displaying of the after upgrade notice on the “What’s New” screen. Shown when the Classic Editor is selected and users cannot switch editors.
1.2
- Fixed switching editors from the Add New (post) screen before a draft post is saved.
- Fixed typo that was appending the edit URL to the
classic-editorquery var. - Changed detecting of WordPress 5.0 to not use version check. Fixes a bug when testing 5.1-alpha.
- Changed the default value of the option to allow users to switch editors to false.
- Added disabling of the Gutenberg plugin and lowered the required WordPress version to 4.9.
- Added
classic_editor_network_default_settingsfilter.
1.1
Fixed a bug where it may attempt to load the Block Editor for post types that do not support editor when users are allowed to switch editors.
1.0
- Updated for WordPress 5.0.
- Changed all “Gutenberg” names/references to “Block Editor”.
- Refreshed the settings UI.
- Removed disabling of the Gutenberg plugin. This was added for testing in WordPress 4.9. Users who want to continue following the development of Gutenberg in WordPress 5.0 and beyond will not need another plugin to disable it.
- Added support for per-user settings of default editor.
- Added support for admins to set the default editor for the site.
- Added support for admins to allow users to change their default editor.
- Added support for network admins to prevent site admins from changing the default settings.
- Added support to store the last editor used for each post and open it next time. Enabled when users can choose default editor.
- Added “post editor state” in the listing of posts on the Posts screen. Shows the editor that will be opened for the post. Enabled when users can choose default editor.
- Added
classic_editor_enabled_editors_for_postandclassic_editor_enabled_editors_for_post_typefilters. Can be used by other plugins to control or override the editor used for a particular post of post type. - Added
classic_editor_plugin_settingsfilter. Can be used by other plugins to override the settings and disable the settings UI.
0.5
- Updated for Gutenberg 4.1 and WordPress 5.0-beta1.
- Removed some functionality that now exists in Gutenberg.
- Fixed redirecting back to the Classic Editor after looking at post revisions.
0.4
- Fixed removing of the “Try Gutenberg” call-out when the Gutenberg plugin is not activated.
- Fixed to always show the settings and the settings link in the plugins list table.
- Updated the readme text.
0.3
- Updated the option from a checkbox to couple of radio buttons, seems clearer. Thanks to @designsimply for the label text suggestions.
- Some general updates and cleanup.
0.2
- Update for Gutenberg 1.9.
- Remove warning and automatic deactivation when Gutenberg is not active.
0.1
Initial release.

