Version Description
- November 23, 2022
- rename to prevent conflicts with other plugin
Download this release
Release Info
Developer | senlin |
Plugin | Classic Editor Addon |
Version | 4.0.2 |
Comparing to | |
See all releases |
Code changes from version 4.0.1 to 4.0.2
- classic-editor-addon.php +3 -3
- readme.txt +18 -17
classic-editor-addon.php
CHANGED
@@ -1,10 +1,10 @@
|
|
1 |
<?php
|
2 |
/**
|
3 |
-
* Plugin Name: Classic Editor
|
4 |
-
* Description: The "Classic Editor
|
5 |
|
6 |
* Author: <a href="https://so-wp.com">Pieter Bos</a>, <a href="https://gschoppe.com">Greg Schoppe</a>
|
7 |
-
* Version: 4.0.
|
8 |
|
9 |
* Requires at least: 4.9
|
10 |
* Tested up to: 6.1
|
1 |
<?php
|
2 |
/**
|
3 |
+
* Plugin Name: Classic Editor +
|
4 |
+
* Description: The "Classic Editor +" plugin disables the block editor, removes enqueued scripts/styles and brings back classic Widgets.
|
5 |
|
6 |
* Author: <a href="https://so-wp.com">Pieter Bos</a>, <a href="https://gschoppe.com">Greg Schoppe</a>
|
7 |
+
* Version: 4.0.2
|
8 |
|
9 |
* Requires at least: 4.9
|
10 |
* Tested up to: 6.1
|
readme.txt
CHANGED
@@ -1,43 +1,39 @@
|
|
1 |
-
=== Classic Editor
|
2 |
Contributors: senlin, gschoppe
|
3 |
-
Tags: gutenberg, block editor, classic editor,
|
4 |
Requires at least: 4.9
|
5 |
Requires PHP: 5.6
|
6 |
Tested up to: 6.1
|
7 |
-
Stable tag: 4.0.
|
8 |
License: GPL-3.0+
|
9 |
License URI: http://www.gnu.org/licenses/gpl-3.0.txt
|
10 |
|
11 |
-
The "Classic Editor
|
12 |
|
13 |
== Description ==
|
14 |
|
15 |
> GDPR-compliant: does not collect any user data
|
16 |
|
17 |
-
The free Classic Editor
|
18 |
|
19 |
<strong>What's New:</strong>
|
20 |
No longer dependent on Classic Editor plugin; you may remove it.
|
21 |
|
22 |
-
|
23 |
|
24 |
-
|
25 |
|
26 |
-
|
27 |
|
28 |
-
|
29 |
-
|
30 |
-
With version 3.1.0 Classic Widgets are back and version 4.0 has seen a complete rewrite of the plugin where the dependency on the Classic Editor plugin has been completely removed.
|
31 |
-
|
32 |
-
Therefore I highly recommend installing this "Classic Editor Plus" plugin.
|
33 |
|
34 |
I support this plugin exclusively through [Github](https://github.com/senlin/classic-editor-addon/issues). 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.
|
35 |
|
36 |
Thanks for your understanding and cooperation.
|
37 |
|
38 |
-
If you like the Classic Editor
|
39 |
|
40 |
-
Classic Editor
|
41 |
|
42 |
== Frequently Asked Questions ==
|
43 |
|
@@ -48,11 +44,11 @@ The release of WordPress 5.0 came with a replacement of the TinyMCE editor you h
|
|
48 |
= Why this plugin? Isn't the purpose of the Classic Editor plugin to disable the new block editor? =
|
49 |
|
50 |
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.
|
51 |
-
This "Classic Editor
|
52 |
|
53 |
= Do I still need the Classic Editor plugin on my site? =
|
54 |
|
55 |
-
Version 4.0 of the Classic Editor
|
56 |
|
57 |
= I have an issue with this plugin, where can I get support? =
|
58 |
|
@@ -60,6 +56,11 @@ Please open an issue on [Github](https://github.com/senlin/classic-editor-addon/
|
|
60 |
|
61 |
== Changelog ==
|
62 |
|
|
|
|
|
|
|
|
|
|
|
63 |
= 4.0.1 =
|
64 |
|
65 |
* November 23, 2022
|
1 |
+
=== Classic Editor + ===
|
2 |
Contributors: senlin, gschoppe
|
3 |
+
Tags: gutenberg, block editor, classic editor, wordpress 5.0, woocommerce, classic widgets
|
4 |
Requires at least: 4.9
|
5 |
Requires PHP: 5.6
|
6 |
Tested up to: 6.1
|
7 |
+
Stable tag: 4.0.2
|
8 |
License: GPL-3.0+
|
9 |
License URI: http://www.gnu.org/licenses/gpl-3.0.txt
|
10 |
|
11 |
+
The "Classic Editor +" plugin disables the block editor, removes enqueued scripts/styles and brings back classic Widgets.
|
12 |
|
13 |
== Description ==
|
14 |
|
15 |
> GDPR-compliant: does not collect any user data
|
16 |
|
17 |
+
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!
|
18 |
|
19 |
<strong>What's New:</strong>
|
20 |
No longer dependent on Classic Editor plugin; you may remove it.
|
21 |
|
22 |
+
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.
|
23 |
|
24 |
+
And if WooCommerce has been installed on the site, "Classic Editor +" removes the block styles of that plugin too.
|
25 |
|
26 |
+
There are no Settings, it simply does what it says on the label.
|
27 |
|
28 |
+
Therefore I highly recommend installing this "Classic Editor +" plugin.
|
|
|
|
|
|
|
|
|
29 |
|
30 |
I support this plugin exclusively through [Github](https://github.com/senlin/classic-editor-addon/issues). 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.
|
31 |
|
32 |
Thanks for your understanding and cooperation.
|
33 |
|
34 |
+
If you like the "Classic Editor +" plugin, please consider leaving a [review](https://wordpress.org/support/view/plugin-reviews/classic-editor-addon?rate=5#postform). Thanks!
|
35 |
|
36 |
+
"Classic Editor +" by [Pieter Bos](https://so-wp.com/plugin/classic-editor-addon) and [Greg Schoppe](https://gschoppe.com).
|
37 |
|
38 |
== Frequently Asked Questions ==
|
39 |
|
44 |
= Why this plugin? Isn't the purpose of the Classic Editor plugin to disable the new block editor? =
|
45 |
|
46 |
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.
|
47 |
+
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.
|
48 |
|
49 |
= Do I still need the Classic Editor plugin on my site? =
|
50 |
|
51 |
+
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.
|
52 |
|
53 |
= I have an issue with this plugin, where can I get support? =
|
54 |
|
56 |
|
57 |
== Changelog ==
|
58 |
|
59 |
+
= 4.0.2 =
|
60 |
+
|
61 |
+
* November 23, 2022
|
62 |
+
* rename to prevent conflicts with other plugin
|
63 |
+
|
64 |
= 4.0.1 =
|
65 |
|
66 |
* November 23, 2022
|