Classic Editor

Descripción

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”).

Capturas

  • 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 settings to select the default editor for the network and allow site admins to change it.
  • The "Switch to Classic Editor" link.

Preguntas frecuentes

Default settings

When activated this plugin will restore the previous (“classic”) WordPress editor and hide the new Block Editor (“Gutenberg”).
These settings can be changed at the Settings => Writing screen.

Default settings for network installation

There are two options:

  • When network-activated this plugin will set the Classic Editor as default and prevent site administrators and users from changing editors.
    The settings can be changed and default network-wide editor can be selected on the Network Settings screen.
  • When not network-activated each site administrator will be able to activate the plugin and choose options for their users.
Cannot find the “Switch to Classic Editor” link

It is in the main Block Editor menu, see this screenshot.

Reseñas

Here’s an idea…

...make this the default WP and make Gutenburg an optional plugin. Don't know if anyone will go for it but it's a thought...

Плагин меня реально спас!!!

Блин! Обновил ВордПресс до версии 5.1.1. Минут 10 сидел вникал в то, как же пользоваться этими блоками в новом редакторе и как перейти в управление конструктора Profit Builder. Не нашел. Да и размещать статьи на свой блог в таком редакторе я категорически отказываюсь! Уже думал перейти на старую версию ВордПресс. Но случилось чудо, и я нашел этот плагин! Спасибо за него огромное! Вот правда!!! И кнопка Profit Builder появилась в редакторе. Фух! Слава тебе, Господи...

Says it all really…

Thank you, thank you, thank you for the classic editor plugin. I've tried to review in the past but I've had problems with my forum account ever since I reviewed Gutenberg (1-star). Today I found out why: Your account was flagged for joining the hate brigade of Gutenberg at the time. The reviews aren't for blogging, brigading and venting, and this is is not a special rule for Gutenberg. So 👋 (Hi) fellow hate brigaders 😂

I wanted to like Gutenberg…

I really did, but I find it distracting and overly complicated when writing a simple block post. This simple plugin saves the day, and judging by the reception, it also has saved the day for a lot of other people too. Building block style editors are undoubtedly the future but I don't know why Gutenberg couln't co-exist within "classic" editor - at least to begin with. Making it either or really limits the flexibility of WordPress IMO.
Read all 603 reviews

Contribuidores y desarrolladores

Este software es de código abierto. Las siguientes personas han contribuido a este plugin.

Contribuidores

“Classic Editor” has been translated into 46 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.

Registro de cambios

1.4

  • On network installations removed the restriction for only network activation.
  • Added support for network administrators to choose the default network-wide editor.
  • Fixed the settings link in the warning on network About screen.
  • Properly added the “Switch to Classic Editor” menu item to the Block Editor menu.

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

Versión inicial.