Skip to content

Commit 119318b

Browse files
senlinsenlin
committed
commit v4.0.1
* November 23, 2022 * use consistent function prefixes * change FAQ readme
1 parent 567d312 commit 119318b

3 files changed

Lines changed: 25 additions & 11 deletions

File tree

‎README.md‎

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
[![plugin version](https://img.shields.io/wordpress/plugin/v/classic-editor-addon.svg)](https://wordpress.org/plugins/classic-editor-addon) [![WP compatibility](https://plugintests.com/plugins/classic-editor-addon/wp-badge.svg)](https://plugintests.com/plugins/classic-editor-addon/latest) [![PHP compatibility](https://plugintests.com/plugins/classic-editor-addon/php-badge.svg)](https://plugintests.com/plugins/classic-editor-addon/latest)
44

5-
###### Last updated on November 22, 2022
5+
###### Last updated on November 23, 2022
66
###### Development version
77
###### requires at least WordPress 4.9
88
###### tested up to WordPress 6.1
@@ -15,7 +15,7 @@ The "Classic Editor Plus" plugin removes enqueued scripts/styles and brings back
1515

1616
> GDPR-compliant: does not collect any user data
1717
18-
The free Classic Editor Plus 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 the fluff!
18+
The free Classic Editor Plus 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!
1919

2020
**What's New:**<br>
2121
No longer dependent on Classic Editor plugin; you may remove it.
@@ -28,7 +28,7 @@ Also, looking at developers protecting the sites of their clients with the Class
2828

2929
Sites running WooCommerce get another style added to the <code><head></code> section of the site. With Classic Editor Plus installed that call is obviously redundant. With version 2.5.0 I introduced a condition that checks for WooCommerce and if active it removes that call. Win!
3030

31-
And with version 3.1.0 Classic Widgets are also back.
31+
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.
3232

3333
Therefore I highly recommend installing this "Classic Editor Plus" plugin.
3434

@@ -48,7 +48,8 @@ The release of WordPress 5.0 came with a replacement of the TinyMCE editor you h
4848

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

51-
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 Plus" simply removes the block editor and all its styling from both frontend and backend.
51+
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.
52+
This "Classic Editor Plus" 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.
5253

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

@@ -65,6 +66,12 @@ Please open an issue on [Github](https://github.com/senlin/classic-editor-addon/
6566

6667
## Changelog
6768

69+
### 4.0.1
70+
71+
* November 23, 2022
72+
* use consistent function prefixes
73+
* change FAQ readme
74+
6875
### 4.0
6976

7077
* November 22, 2022

‎classic-editor-addon.php‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
* Description: The "Classic Editor Plus" plugin removes enqueued scripts/styles and brings back classic Widgets.
55
66
* Author: <a href="https://so-wp.com">Pieter Bos</a>, <a href="https://gschoppe.com">Greg Schoppe</a>
7-
* Version: 4.0
7+
* Version: 4.0.1
88
99
* Requires at least: 4.9
1010
* Tested up to: 6.1
@@ -35,9 +35,9 @@ function cea_deactivate_ce() {
3535
}
3636
}
3737

38-
add_action( 'wp_enqueue_scripts', 'classic_editor_addon_remove_block_styles', 100 );
38+
add_action( 'wp_enqueue_scripts', 'cea_remove_block_styles', 100 );
3939

40-
function classic_editor_addon_remove_block_styles() {
40+
function cea_remove_block_styles() {
4141

4242
wp_dequeue_style( 'wp-block-library' );
4343
wp_deregister_style( 'wp-block-library' );

‎readme.txt‎

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Tags: gutenberg, block editor, classic editor, addon, wordpress 5.0, woocommerce
44
Requires at least: 4.9
55
Requires PHP: 5.6
66
Tested up to: 6.1
7-
Stable tag: 4.0
7+
Stable tag: 4.0.1
88
License: GPL-3.0+
99
License URI: http://www.gnu.org/licenses/gpl-3.0.txt
1010

@@ -14,7 +14,7 @@ The "Classic Editor Plus" plugin removes enqueued scripts/styles and brings back
1414

1515
> GDPR-compliant: does not collect any user data
1616

17-
The free Classic Editor Plus 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 the fluff!
17+
The free Classic Editor Plus 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!
1818

1919
<strong>What's New:</strong>
2020
No longer dependent on Classic Editor plugin; you may remove it.
@@ -27,7 +27,7 @@ Also, looking at developers protecting the sites of their clients with the Class
2727

2828
Sites running WooCommerce get another style added to the <code><head></code> section of the site. With Classic Editor Plus installed that call is obviously redundant. With version 2.5.0 I introduced a condition that checks for WooCommerce and if active it removes that call. Win!
2929

30-
And with version 3.1.0 Classic Widgets are also back.
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.
3131

3232
Therefore I highly recommend installing this "Classic Editor Plus" plugin.
3333

@@ -47,7 +47,8 @@ The release of WordPress 5.0 came with a replacement of the TinyMCE editor you h
4747

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

50-
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 Plus" simply removes the block editor and all its styling from both frontend and backend.
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 Plus" 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.
5152

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

@@ -59,6 +60,12 @@ Please open an issue on [Github](https://github.com/senlin/classic-editor-addon/
5960

6061
== Changelog ==
6162

63+
= 4.0.1 =
64+
65+
* November 23, 2022
66+
* use consistent function prefixes
67+
* change FAQ readme
68+
6269
= 4.0 =
6370

6471
* November 22, 2022

0 commit comments

Comments
 (0)