Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

Classic Editor · Version history

Classic Editor changelog and version history

Latest version
1.7.0
May 28, 2026 (5 months ago)
Releases
20
since 2017
In the last year
2
about one every 171 days
Tested up to
WordPress 7.0.8
PHP 5.2.4 or later

Releases each year

  • 20172 releases
  • 20187 releases
  • 20191 release
  • 20201 release
  • 20212 releases
  • 20221 release
  • 20244 releases
  • 20251 release
  • 20261 release

20261 release

  1. Classic Editor 1.7.0Latest

    • Added a hotfix for crowded elements in the publishing actions area in WordPress 7.0. See Core-65286 for more information.

20251 release

  1. Classic Editor 1.6.7

    • Fixed loading of script translations when post.js is replaced in WordPress 6.7.1.

20244 releases

  1. Classic Editor 1.6.6

    • Added fix for selecting/deselecting multiple unwanted categories in WordPress 6.7.1 when clicking on a category checkbox on the old Edit Post screen.
  2. Classic Editor 1.6.5

    • Added fix for Safari 18 negative horizontal margin on floats.
  3. Classic Editor 1.6.4

    • Added support for administrators to choose the default editor for other users.
  4. Classic Editor 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.

20221 release

  1. Classic Editor 1.6.2

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

20212 releases

  1. Classic Editor 1.6.1

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

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

20201 release

  1. Classic Editor 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.

20191 release

  1. Classic Editor 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.

20187 releases

  1. Classic Editor 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.
  2. Classic Editor 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.
  3. Classic Editor 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.
  4. Classic Editor 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.
  5. Classic Editor 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.
  6. Classic Editor 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.
  7. Classic Editor 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.

20172 releases

  1. Classic Editor 0.2

    • Update for Gutenberg 1.9.
    • Remove warning and automatic deactivation when Gutenberg is not active.
  2. Classic Editor 0.1

    • Initial release.

Questions about Classic Editor’s releases

What is the latest version of Classic Editor?

1.7.0, released on May 28, 2026 (5 months ago). It’s tested up to WordPress 7.0.8 and needs PHP 5.2.4 or later.

How often is Classic Editor updated?

2 releases in the last year, about one every 171 days. Its first release on WordPress.org dates from December 2017.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in Classic Editor’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.