

Why this addon? Isn’t the purpose of the Classic Editor plugin to disable the new block editor? More information can be found on the WP 5.0 release post. Some find it an improvement, others don’t. The release of WordPress 5.0 comes with a replacement of the TinyMCE editor you have gotten used to.

Thanks!Ĭlassic Editor Addon by Pieter Bos and Greg Schoppe.įAQ What is this new block editor that ships with WordPress 5.0? If you like the Classic Editor Addon plugin, please consider leaving a review. Thanks for your understanding and cooperation. You can also browse through open and closed issues to find what you are looking for and perhaps even help others. Therefore, if you have any questions, need help and/or want to make a feature request, please open an issue here. We support this plugin exclusively through Github. Therefore we highly recommend installing this “Classic Editor Addon” plugin, which will automatically install the “Classic Editor” plugin and remove its settings. With version 2.5.0 we introduce a condition that checks for WooCommerce and if active it removes that call. With the Classic Editor Addon installed that call is obviously redundant. Sites running WooCommerce get another style added to the section of the site. 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.Īlso, 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. Since version 0.0.4 of the “Classic Editor” plugin, it finally set the default setting to actually using the Classic Editor. 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. Please pay attention that the minimum PHP version to use our plugin is 5.6. Rollback removal of WooCommerce block-ui scripts Install it now on sites and the UX remains the same as you are used to! The free Classic Editor Addon plugin is targeted at everyone who is not yet ready for the new editing experience that has been introduced in WordPress 5.0. GDPR-compliant: does not collect any user data
