Classic Editor

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.
By default, this plugin hides all functionality available in the new Block Editor (“Gutenberg”).

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.

Classic Editor is an official WordPress plugin, and will be maintained until at least 2022.

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

A much needed plugin, alas

Thank you so much for this plugin. I’ve been using it for months on the dozens of websites I manage for clients and it’s really saved my bacon. I build bespoke applications on the WP framework, with lots of custom interfaces, custom permissions, ACF pro custom fields, workflows, etc. None of my clients want to touch Gutenberg with a 5 foot pole, and neither do I: it’s abysmal as a writing experience, it’s abysmal as a development framework, and it’s abysmal in terms of migration hurdles.

By the way, many of my clients are in the news industry. One team is literally composed of professional journalists who write 200+ posts per week on a WordPress-based backoffice. They actually tried Gutenberg and they don’t want it at all. That should tell you something.

Automattic really dropped the ball here with this rushed deployment, and in addition it seems that they antagonized developers, aka the people most able to spread the word about Gutenberg to end users, to help users install it and use it, and to develop on it.

From a freelance developer: shame on you, Automattic.

Saves us from the madness! This should be the default editor

As others have said, this should be the default editor and the new ‘block’ thing should be a plugin. Seems a crazy idea to push that new editor on everyone. I hope you will re-consider this (but won’t hold my breath).

If this plugin wasn’t available then I would be looking for something to replace wordpress.

5 stars for the route out of the madness.

But perhaps it will be better to switch to ClassicPress https://www.classicpress.net/

Saved my site

The new gutenberg editor broke many of my posts and pages, it’s not ready for release yet. Some pages returned with “unexpected error, can’t display content”. Worst thing for me, the option for “Don’t display featured image on single posts” is missing in gutenberg. As soon as i updated a post with gutenberg, the image got displayed on the post, something i do not want.
The classic editor made everything work again 🙂

THAT FEELING WHEN YOU INSTALL THIS AND GUTENBERG IS DESTROYED

Thank goodness for this plugin! I updated to version 5 and then all of a sudden I couldn’t see anything else but the disaster that is gutenberg.

Editing via blocks? Really?

There’s a reason why I’m on wordpress and not on wix.

Gutenberg should be an option and shouldn’t be forced down our throats.

It’s bad.

Divi is way more awesome. What gutenberg should be.

Read all 204 reviews

Contributors & Developers

“Classic Editor” adalah perisian sumber terbuka. Orang-orang berikut telah menyumbang kepada pemalam ini.

Penyumbang

“Classic Editor” telah diterjemahkan ke dalam 39 penempatan. Terima kasih kepada para penterjemah untuk terjemahan mereka.

Translate “Classic Editor” into your language.

Berminat dalam pembangunan?

Layari kod, periksa repositori SVN, atau langgani log pembangunan dengan 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-editor query 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_settings filter.

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_post and classic_editor_enabled_editors_for_post_type filters. Can be used by other plugins to control or override the editor used for a particular post of post type.
  • Added classic_editor_plugin_settings filter. 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.