Classic Editor Addon - Version 2.2.0

Version Description

  • December 12, 2018
  • rewrite of function that removes settings of the Classic Editor plugin
Download this release

Release Info

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

Code changes from version 2.1.1 to 2.2.0

Files changed (2) hide show
  1. classic-editor-addon.php +7 -6
  2. readme.txt +19 -14
classic-editor-addon.php CHANGED
@@ -1,10 +1,10 @@
1
  <?php
2
  /**
3
  * Plugin Name: Classic Editor Addon
4
- * Description: This free "Classic Editor Addon" plugin makes sure that Gutenberg cannot be accidentally activated even while the "Classic Editor" plugin is active. See readme.txt for more details.
5
 
6
  * Author: <a href="https://so-wp.com">Pieter Bos</a>, <a href="https://gschoppe.com">Greg Schoppe</a>
7
- * Version: 2.1.1
8
 
9
  * Requires at least: 4.9
10
  * Tested up to: 5.0
@@ -30,14 +30,15 @@ include_once( __DIR__ . '/vendor/autoload.php' );
30
  WP_Dependency_Installer::instance()->run( __DIR__ );
31
 
32
  add_action( 'plugins_loaded', 'classic_editor_addon_post_init', 20, 0 );
 
33
  function classic_editor_addon_post_init() {
34
 
35
- if ( function_exists( 'classic_editor_init_actions' ) ) {
36
  /**
37
- * Remove Settings link to the settings from the Plugins screen (L277).
38
  */
39
- remove_filter( 'plugin_action_links', 'classic_editor_add_settings_link' );
40
- remove_action( 'admin_init', 'classic_editor_admin_init' );
41
  }
42
 
43
  }
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 even while the "Classic Editor" plugin is active. See readme.txt for more details.
5
 
6
  * Author: <a href="https://so-wp.com">Pieter Bos</a>, <a href="https://gschoppe.com">Greg Schoppe</a>
7
+ * Version: 2.2.0
8
 
9
  * Requires at least: 4.9
10
  * Tested up to: 5.0
30
  WP_Dependency_Installer::instance()->run( __DIR__ );
31
 
32
  add_action( 'plugins_loaded', 'classic_editor_addon_post_init', 20, 0 );
33
+
34
  function classic_editor_addon_post_init() {
35
 
36
+ if ( class_exists( 'Classic_Editor' ) ) {
37
  /**
38
+ * Remove Settings link to the settings from the Plugins screen.
39
  */
40
+ remove_filter( 'plugin_action_links', array( 'Classic_Editor', 'add_settings_link' ) );
41
+ remove_action( 'admin_init', array( 'Classic_Editor', 'register_settings' ) );
42
  }
43
 
44
  }
readme.txt CHANGED
@@ -1,30 +1,30 @@
1
  === Classic Editor Addon ===
2
  Contributors: senlin, gschoppe
3
- Tags: gutenberg, classic editor, addon
4
  Requires at least: 4.9
5
  Requires PHP: 5.3
6
  Tested up to: 5.0
7
- Stable tag: 2.1.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 Gutenberg 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 Gutenberg and/or who does not want to bother clients with Gutenberg. Install it now on sites and by the time WP 5.0 is released, the UX remains the same as you are used to!
18
 
19
  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.
20
 
21
- 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 Gutenberg, then we don't see the need for such a Settings page.
22
 
23
- 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 Gutenberg adds a lot of undesirable comments, tags and what not to the content.
24
 
25
  Therefore we highly recommend installing this "Classic Editor Addon" plugin, which will automatically download the “Classic Editor” plugin to enable easy install. It removes the Settings link from the main Plugins page and removes the plugin's Settings from the Settings > Writing screen.
26
 
27
- 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 over at Github. You can also browse through open and closed issues to find what you are looking for and perhaps even help others.
28
 
29
  Thanks for your understanding and cooperation.
30
 
@@ -34,21 +34,21 @@ Classic Editor Addon by [Pieter Bos](https://so-wp.com/plugin/classic-editor-add
34
 
35
  == Frequently Asked Questions ==
36
 
37
- = What is Gutenberg? =
38
 
39
- Gutenberg is a new editing experience that will drop with WordPress 5.0, whether we like it or not. More information can be found on the [Gutenberg FAQ](https://wordpress.org/gutenberg/handbook/reference/faq/).
40
 
41
- = Why this addon? Isn't the purpose of the Classic Editor plugin to disable Gutenberg? =
42
 
43
- When it was released initially, the "Classic Editor" plugin, by Andrew Ozz, didn't completely disable Gutenberg 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".
44
 
45
- = How does this compare to other plugins that disable Gutenberg? =
46
 
47
- Great question! "Classic Editor" is the official plugin for removing Gutenberg, and the install count is apparently being used as a metric to gauge success of the Gutenberg project. So, although other plugins exist to force-disable Gutenberg, 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 Gutenberg itself, it just removes the Settings page of the "Classic Editor" plugin, making it easier to mass-install classic editor.
48
 
49
  = The plugin doesn't do anything! =
50
 
51
- Is Gutenberg active on the site and do you have the Classic Editor plugin installed? Those two are requirements for this addon plugin to do anything. If you have and the plugin still doesn't do anything, then please open a [support ticket](https://github.com/senlin/classic-editor-addon/issues).
52
 
53
  = I have an issue with this plugin, where can I get support? =
54
 
@@ -56,6 +56,11 @@ Please open an issue on [Github](https://github.com/senlin/classic-editor-addon/
56
 
57
  == Changelog ==
58
 
 
 
 
 
 
59
  = 2.1.1 =
60
 
61
  * October 25, 2018
1
  === Classic Editor Addon ===
2
  Contributors: senlin, gschoppe
3
+ Tags: gutenberg, block editor, classic editor, addon, wordpress 5.0
4
  Requires at least: 4.9
5
  Requires PHP: 5.3
6
  Tested up to: 5.0
7
+ Stable tag: 2.2.0
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
  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.
20
 
21
+ 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.
22
 
23
+ 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.
24
 
25
  Therefore we highly recommend installing this "Classic Editor Addon" plugin, which will automatically download the “Classic Editor” plugin to enable easy install. It removes the Settings link from the main Plugins page and removes the plugin's Settings from the Settings > Writing screen.
26
 
27
+ 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.
28
 
29
  Thanks for your understanding and cooperation.
30
 
34
 
35
  == Frequently Asked Questions ==
36
 
37
+ = What is this new block editor that ships with WordPress 5.0? =
38
 
39
+ 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/).
40
 
41
+ = Why this addon? Isn't the purpose of the Classic Editor plugin to disable the new block editor? =
42
 
43
+ 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".
44
 
45
+ = How does this compare to other plugins that disable the new block editor? =
46
 
47
+ 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.
48
 
49
  = The plugin doesn't do anything! =
50
 
51
+ Has the site been updated to WordPress 5.0 and do you have the Classic Editor plugin installed? Those two are requirements for this addon plugin to do anything. If you have and the plugin still doesn't do anything, then please open a [support ticket](https://github.com/senlin/classic-editor-addon/issues).
52
 
53
  = I have an issue with this plugin, where can I get support? =
54
 
56
 
57
  == Changelog ==
58
 
59
+ = 2.2.0 =
60
+
61
+ * December 12, 2018
62
+ * rewrite of function that removes settings of the Classic Editor plugin
63
+
64
  = 2.1.1 =
65
 
66
  * October 25, 2018