senlin / classic-editor-addon

This free "Classic Editor Addon" plugin makes sure that Gutenberg cannot be accidentally activated even while the "Classic Editor" plugin is active.
GNU General Public License v3.0
20 stars 5 forks source link
classic editor gutenberg plugin wordpress

Classic Editor +

plugin version WP compatibility PHP compatibility

Last updated on August 22, 2024
Development version
requires at least WordPress 4.9
tested up to WordPress 6.6
min. PHP version: 5.6
Authors: Pieter Bos & Greg Schoppe

The "Classic Editor +" plugin disables the block editor, removes enqueued scripts/styles and brings back classic Widgets.

Description

GDPR-compliant: does not collect any user data

The free "Classic Editor +" plugin is targeted at everyone who does not want to use the WP Block Editor (Gutenberg), introduced in WordPress 5.0. Install it now on sites and the UX remains the same as you are used to without redundant styling being added to the frontend of your site!

What's New:
Removes WP Patterns

This plugin simply disables the WP Block Editor, removes any and all styling from both front- and backend and disables the block editor for widgets too.

And if WooCommerce and/or WPML are installed on the site, "Classic Editor +" removes the block styles of those plugins too.

There are no Settings, it simply does what it says on the label.

Therefore I highly recommend installing this "Classic Editor +" plugin.

I 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 +" plugin, please consider leaving a review. Thanks!

"Classic Editor +" by Pieter Bos and Greg Schoppe.

WPML Compatible

WPML compatible since February 2023.

Frequently Asked Questions

What is the WP block editor?

The release of WordPress 5.0 came with a replacement of the TinyMCE editor you had gotten used to for adding or editing content. 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?

The Classic Editor plugin does not remove any of the frontend styling, even when one selects the option to disable the block editor. In terms of site optimisation that is not good practice. This "Classic Editor +" simply removes the block editor and all its styling from both frontend and backend and if your site uses WooCommerce, it also removes block styling related to that from the frontend.

Do I still need the Classic Editor plugin on my site?

Version 4.0 of the "Classic Editor +" plugin has been a complete rewrite (and simplification) and it is no longer depending on the Classic Editor plugin. When the latter is active, it will be deactivated and then you can safely remove it.

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

Please open an issue on Github

License

Changelog

4.4.0

4.3.0

4.2.0

4.1.1

4.1.0

4.0.2

4.0.1

4.0

3.1.0

3.0.1

3.0.0

2.6.4

2.6.3

2.6.2

2.6.1

2.6.0

2.5.0

2.4.0

2.3.1

2.3.0

2.2.0

2.1.1

2.1.0

2.0.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

Upgrade Notice

2.0.0