This free "Classic Editor Addon" plugin makes sure that Gutenberg cannot be accidentally activated even while the "Classic Editor" plugin is active.
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
assets
vendor
LICENSE
README.md
classic-editor-addon.php
composer.json
composer.lock
readme.txt
wp-dependencies.json

README.md

Classic Editor Addon

plugin version

Last updated on December 17, 2018
Development version
requires at least WordPress 4.9
tested up to WordPress 5.0.1
min. PHP version: 5.4
Authors: Pieter Bos & Greg Schoppe

This free "Classic Editor Addon" plugin makes sure that the new block editor cannot be accidentally activated even while the "Classic Editor" plugin is active.

Description

GDPR-compliant: does not collect any user data

The free Classic Editor Addon plugin is targeted at everyone who is not yet ready for the new block editor that has been introduced in WordPress 5.0. Install it now on sites and the UX remains the same as you are used to!

The reason we released the "Classic Editor Addon" plugin is because in the beginning the "Classic Editor" plugin did not what it said on the label.

Since version 0.0.4 of the "Classic Editor" plugin, it finally set the default setting to actually using the Classic Editor. It still contains a Settings page though and if the purpose of people is to get the Classic Editor instead of using the new block editor, then we don't see the need for such a Settings page.

Also, if we look at developers protecting the sites of their clients with the Classic Editor, they certainly don't want their clients to accidentally turn off the Classic Editor as the new block editor adds a lot of undesirable comments, tags and what not to the content.

Therefore we highly recommend installing this "Classic Editor Addon" plugin, which will automatically download the “Classic Editor” plugin to enable easy install. It removes the Settings link from the main Plugins page and removes the plugin's Settings from the Settings > Writing screen.

We support this plugin exclusively through Github. Therefore, if you have any questions, need help and/or want to make a feature request, please open an issue here. You can also browse through open and closed issues to find what you are looking for and perhaps even help others.

Thanks for your understanding and cooperation.

If you like the Classic Editor Addon plugin, please consider leaving a review. Thanks!

Classic Editor Addon by Pieter Bos and Greg Schoppe.

Frequently Asked Questions

What is this new block editor that ships with WordPress 5.0?

The release of WordPress 5.0 comes with a replacement of the TinyMCE editor you have gotten used to. Some find it an improvement, others don't. More information can be found on the WP 5.0 release post.

Why this addon? Isn't the purpose of the Classic Editor plugin to disable the new block editor?

When it was released initially, the "Classic Editor" plugin, by Andrew Ozz and other "WordPress Contributors", didn't completely disable the new block editor without changing settings. Since version 0.0.4 it does, but it still comes with Settings. The "Classic Editor Addon" is a second plugin that makes sure the Settings are gone, so they cannot be accidentally triggered and "bring down the skies".

How does this compare to other plugins that disable the new block editor?

Great question! "Classic Editor" is the official plugin for removing the new block editor, and the install count is apparently being used as a metric to gauge success of the project. So, although other plugins exist to force-disable the new block editor, using them doesn't properly notify the WP Core team of the number of issues users are having, that is why "Classic Editor Addon" doesn't disable the new block editor itself, it just removes the Settings page of the "Classic Editor" plugin, making it easier to mass-install the "Classic Editor" plugin.

The plugin doesn't do anything!

Has the site been updated to WordPress 5.0 and do you have the Classic Editor plugin installed? Those two are requirements for this addon plugin to do anything. If you have and the plugin still doesn't do anything, then please open a support ticket.

I have an issue with this plugin, where can I get support?

Please open an issue on Github

License

Changelog

2.3.1

  • December 17, 2018
  • increase minimum PHP version to 5.4 due to introduction new shorthand syntax of WP Dependency Installer update in 2.3.0

2.3.0

  • December 14, 2018
  • version update WP Dependency Installer
  • add parameter "optional": false as a workaround to fix issue #4

2.2.0

  • December 12, 2018
  • rewrite of function that removes settings of the Classic Editor plugin

2.1.1

  • October 25, 2018
  • fix typo which addresses issue #3

2.1.0

  • August 28, 2018
  • remove functions that have become redundant since 0.0.4 release of Classic Editor plugin
  • rewrite readme files

2.0.0

  • July 16, 2018
  • add WP Dependency Installer to facilitate with installing and activating Classic Editor plugin (changed color of admin notice to blue)
  • adjust minimum PHP version (to 5.3) due to addition of WP Dependency Installer

1.4.0

  • July 12, 2018
  • fix issue #2
  • adjust readme text and FAQs

1.3.0

  • July 8, 2018
  • release of plugin on WordPress Plugin Directory, ready for the world :)

1.2.0

  • early July, 2018
  • more feature/function/code improvements by both Pieter & Greg

1.1.0

1.0.0

Upgrade Notice

2.0.0

  • now the plugin requires PHP 5.3 due to addition of WP Dependency Installer