Classic Editor Addon - Version 3.1.0

Version Description

  • October 27, 2022
  • integrate Classic Widgets filters
Download this release

Release Info

Developer senlin
Plugin Icon wp plugin Classic Editor Addon
Version 3.1.0
Comparing to
See all releases

Code changes from version 3.0.1 to 3.1.0

Files changed (2) hide show
  1. classic-editor-addon.php +14 -3
  2. readme.txt +21 -20
classic-editor-addon.php CHANGED
@@ -1,13 +1,13 @@
1
  <?php
2
  /**
3
  * Plugin Name: Classic Editor Addon
4
- * Description: This free "Classic Editor Addon" plugin makes sure that the new block editor cannot be accidentally activated and blocks the calls to additional styles from the <code>&lt;head&gt;</code> (frontend). See README for details.
5
 
6
  * Author: <a href="https://so-wp.com">Pieter Bos</a>, <a href="https://gschoppe.com">Greg Schoppe</a>
7
- * Version: 3.0.1
8
 
9
  * Requires at least: 4.9
10
- * Tested up to: 5.9
11
 
12
  * License: GPL-3.0+
13
  * License URI: http://www.gnu.org/licenses/gpl-3.0.txt
@@ -54,6 +54,17 @@ function classic_editor_addon_post_init() {
54
  */
55
  remove_filter( 'plugin_action_links', array( 'Classic_Editor', 'add_settings_link' ) );
56
  remove_action( 'admin_init', array( 'Classic_Editor', 'register_settings' ) );
 
 
 
 
 
 
 
 
 
 
 
57
  }
58
 
59
  }
1
  <?php
2
  /**
3
  * Plugin Name: Classic Editor Addon
4
+ * Description: The "Classic Editor Addon" plugin removes enqueued scripts/styles and also 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: 3.1.0
8
 
9
  * Requires at least: 4.9
10
+ * Tested up to: 6.1
11
 
12
  * License: GPL-3.0+
13
  * License URI: http://www.gnu.org/licenses/gpl-3.0.txt
54
  */
55
  remove_filter( 'plugin_action_links', array( 'Classic_Editor', 'add_settings_link' ) );
56
  remove_action( 'admin_init', array( 'Classic_Editor', 'register_settings' ) );
57
+
58
+ /**
59
+ * Bring back Classic Widgets
60
+ *
61
+ * @since 3.1.0
62
+ * @src: https://plugins.svn.wordpress.org/classic-widgets/tags/0.3/classic-widgets.php
63
+ */
64
+ // Disable the block editor from managing widgets in the Gutenberg plugin.
65
+ add_filter( 'gutenberg_use_widgets_block_editor', '__return_false' );
66
+ // Disable the block editor from managing widgets.
67
+ add_filter( 'use_widgets_block_editor', '__return_false' );
68
  }
69
 
70
  }
readme.txt CHANGED
@@ -1,37 +1,37 @@
1
  === Classic Editor Addon ===
2
  Contributors: senlin, gschoppe
3
- Tags: gutenberg, block editor, classic editor, addon, wordpress 5.0, woocommerce
4
  Requires at least: 4.9
5
  Requires PHP: 5.6
6
  Tested up to: 6.1
7
- Stable tag: 3.0.1
8
  License: GPL-3.0+
9
  License URI: http://www.gnu.org/licenses/gpl-3.0.txt
10
 
11
- 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.
12
 
13
  == Description ==
14
 
15
  > GDPR-compliant: does not collect any user data
16
 
17
- 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. Install it now on sites and the UX remains the same as you are used to!
18
 
19
  <strong>What's New:</strong>
20
- Replaced dependency library with simple dependency check/notice
21
 
22
- Please pay attention that the minimum PHP version to use our plugin is <strong>5.6</strong>.
23
 
24
- 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.
25
 
26
- 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.
27
 
28
- 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.
29
 
30
- Sites running WooCommerce get another style added to the <code><head></code> section of the site. With the Classic Editor Addon installed that call is obviously redundant. With version 2.5.0 we introduce a condition that checks for WooCommerce and if active it removes that call. Win!
31
 
32
- Therefore we highly recommend installing this "Classic Editor Addon" plugin, which will automatically install the “Classic Editor” plugin and remove its settings.
33
 
34
- We 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
 
@@ -43,15 +43,11 @@ Classic Editor Addon by [Pieter Bos](https://so-wp.com/plugin/classic-editor-add
43
 
44
  = What is this new block editor that ships with WordPress 5.0? =
45
 
46
- 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](https://wordpress.org/news/2018/12/bebo/).
47
 
48
  = Why this addon? Isn't the purpose of the Classic Editor plugin to disable the new block editor? =
49
 
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 Addon" is a second plugin that makes sure the Settings are gone, so they cannot be accidentally triggered and "bring down the skies".
51
-
52
- = How does this compare to other plugins that disable the new block editor? =
53
-
54
- 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.
55
 
56
  = The plugin doesn't do anything! =
57
 
@@ -63,6 +59,11 @@ Please open an issue on [Github](https://github.com/senlin/classic-editor-addon/
63
 
64
  == Changelog ==
65
 
 
 
 
 
 
66
  = 3.0.1 =
67
 
68
  * January 24, 2022
@@ -174,6 +175,6 @@ Please open an issue on [Github](https://github.com/senlin/classic-editor-addon/
174
 
175
  == Upgrade Notice ==
176
 
177
- = 2.0.0 =
178
 
179
- * now the plugin requires PHP 5.3 due to addition of WP Dependency Installer
1
  === Classic Editor Addon ===
2
  Contributors: senlin, gschoppe
3
+ Tags: gutenberg, block editor, classic editor, addon, 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: 3.1.0
8
  License: GPL-3.0+
9
  License URI: http://www.gnu.org/licenses/gpl-3.0.txt
10
 
11
+ The "Classic Editor Addon" plugin removes enqueued scripts/styles and also brings back classic Widgets.
12
 
13
  == Description ==
14
 
15
  > GDPR-compliant: does not collect any user data
16
 
17
+ The free Classic Editor Addon 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!
18
 
19
  <strong>What's New:</strong>
20
+ Brings back Classic Widgets
21
 
22
+ The reason I released the "Classic Editor Addon" plugin is because in the beginning the "Classic Editor" plugin did not what it said on the label.
23
 
24
+ 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 there is no need for such a Settings page.
25
 
26
+ Also, looking 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 html comments, tags and what not to the content.
27
 
28
+ Sites running WooCommerce get another style added to the <code><head></code> section of the site. With the Classic Editor Addon 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!
29
 
30
+ And with version 3.1.0 Classic Widgets are also back.
31
 
32
+ Therefore I highly recommend installing this "Classic Editor Addon" plugin. As it is an addon, you will also need to have the main Classic Editor plugin installed.
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
 
43
 
44
  = What is this new block editor that ships with WordPress 5.0? =
45
 
46
+ 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](https://wordpress.org/news/2018/12/bebo/).
47
 
48
  = Why this addon? Isn't the purpose of the Classic Editor plugin to disable the new block editor? =
49
 
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 Addon" is a second plugin (hence the name "addon") that makes sure the Settings are gone, so they cannot be accidentally triggered and "bring down the skies".
 
 
 
 
51
 
52
  = The plugin doesn't do anything! =
53
 
59
 
60
  == Changelog ==
61
 
62
+ = 3.1.0 =
63
+
64
+ * October 27, 2022
65
+ * integrate Classic Widgets filters
66
+
67
  = 3.0.1 =
68
 
69
  * January 24, 2022
175
 
176
  == Upgrade Notice ==
177
 
178
+ = 3.1.0 =
179
 
180
+ * includes Classic Widgets