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.

Classic Editor is an official WordPress plugin, and will be fully supported and maintained until 2024, 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

FAQ

Default settings

When activated and when using a classic (non-block) theme, 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 and when using a classic (non-block) theme, 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.

Does this work with full site editing and block themes?

No, as block themes rely on blocks. See Block themes article for more information.

Reviews

Must have

mykola4599 October 20, 2024

Since I don’t understand the Gutenberg layout, this plugin works for me just fine

A must-have

George Kpax October 2, 2024

This is the first plugin I install in every WordPress website I setup or manage. This should have been a core option in my opinion. Glad we weren’t forced to use Gutenberg. Thanks!

Fejlesztési javaslat

hobbiasztalos September 28, 2024

Imádom a klasszikus szerkeszt?t, mert nincs tele felesleges formázásokkal, blokkokkal. Nem is akarok átállni blokkszerkeszt?re. Viszont van ennek a szerkeszt?nek is hibája, a média tárból egy kép kiválasztása túl sok kattintást igényel. Egy olyan gomb kellene a szerkeszt?be amivel egyb?l a kép fel?tésére kattintva egyb?l a bejegyzésbe rakja a képet, t?bblet kattintás nélkül. A kategóriák kiválasztása is lehetne k?nnyebb. Ez f?leg ott probléma ahol sok kategória és alkategória van.

Much better than block editor

inge12 September 27, 2024

I find the block editor clunky compared to the Classic Editor for any text-dense applications. The Block Editor was a downgrade from the functional and versatile Classic Editor. Please keep the Classic Editor going and update as necessary.

Essential, couldn’t use WP without

exinator4 September 26, 2024 1 reply

On all client sites, Classic Editor is the first thing I reach for. Blocks may be cool but to non-technical users they’re not even close to being as approachable and I regularly get feedback that it’s confusing. Sometimes, what ain’t broke is just worth keeping.

Best Ever! Blocks are so complicated

Surferweb September 25, 2024

Classic Editor is the only option for writers. If you want to paste something in blocks you are dead. if you want to optmize titles , subtitles and pargraphs yow are dead. For a special page layout Blocks maybe will be ok in a distant future. But so many page editors do a grater job. Should buy elementor or beaver builder as you did with woocommerce.

Contributors & Developers

Changelog

1.6.5

• Added fix for Safari 18 negative horizontal margin on floats.

1.6.4

• Added support for administrators to choose the default editor for other users.

1.6.3

• Added some WPCS fixes, props NicktheGeek on GitHub.
• Updated “Tested up to” in the readme and removed it from classic-editor.php. This should fix false positive errors in security plugins in the future.

1.6.2

• Fixed bug that was preventing saving of the last used editor.

1.6.1

• Fixed a warning on the block editor based widgets screen.
• Fixed use of a deprecated filter.

1.6

• Updated for WordPress 5.5.
• Fixed minor issues with calling deprecated functions, needlessly registering uninstall hook, and capitalization of some strings.

1.5

• Updated for WordPress 5.2 and Gutenberg 5.3.
• Enhanced and fixed the “open posts in the last editor used to edit them” logic.
• Fixed adding post state so it can easily be accessed from other plugins.

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

Initial release.