Classic Editor

Skildring

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

Skjermbilete

  • 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.

Vanlege spm.

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.

Omtalar

15. oktober 2019
Bring back the classic editor as the default. Thankfully somebody developed this little life saver!
14. oktober 2019
This Plugin is really good for those who had difficulties with this new Gutenberg interface, who knows why it was implemented in WordPress. However, despite being a very good alternative, it has a serious problem with inserting highlighted images in the posts. I hope the developers pay attention to this, because every time I need to insert an image, I have to disable the plugin to be able to post it. Apparently, it wasn't just me who noticed this problem. But it is an application that I recommend. However, it has this flaw that kills all the "magic" it provides.
10. oktober 2019
The Classic Editor is so much easier to use than the new default editor Gutenberg. Whether you're a developer and need to write custom plugins or you're an end-user who is familiar with using MS Word or Google Docs, this is for you. It is simple to use, quick to learn, and easy to expand. After struggling with Gutenberg a few times, all of the WordPress based websites I build have this plugin installed by default. This way the customers can update their own sites with very little training and I don't have to wrestle with the editor performing content updates for them myself. The Classic Editor (tinyMCE) should be the default editor again.
9. oktober 2019
The classic editor is much better than Gutenberg! I'm also experimenting with other plugins like "disable gutenberg", "wp downgrader" as my theme has the best block editor I've ever found built right in (Divi). Also started playing with classicpress, (the WordPress fork of version 4.9.x) and it's working (and listening to its users) like I would expect WordPress to do. If you can use MS word, you can use the classic editor!
8. oktober 2019
Read into the "advantages" of gutenberg just to try to give it another catch. I'll save you some time, don't. It's Elementor lite with 1800 issues on git! Just because a developer thinks it has more features, doesn't mean it works in a real business where people need to get sh~t done and not play with blocks all day. Yes, classic editor is not "powerful" but it's a pure and simple "block" that has what's needed. Easy to understand and use. Accessible for non-developers, virtual assistants and productivity fiends. make classic default again! or try gutenberg 2019 and be disappointed AGAIN
Les alle 712 omtalar

Bidragsytarar og utviklarar

“Classic Editor” is open source software. The following people have contributed to this plugin.

Contributors

“Classic Editor” er omsett til 50 språk. Takk til omsetjarane for bidraga deira.

Omset “Classic Editor” til ditt eige språk.

Interested in development?

Les kjeldekoden, sjekk SVN-lageret eller abonner på utviklingsloggen med RSS.

Endringslogg

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.