Multisite request

  • Hi,

    Please allow this plugin to be activated on a site by site basis in a Multisite setup. Currently it’s only possible to activate the plugin for the entire network and then allow admins to choose their own preference, which is not ideal in some cases.

    Unless a second option is added to the Network settings page when the option “Allow site admins to change settings” is checked, like
    “Default editor: Gutenberg | Classic”, to allow the new editor to remain the default and still allow single sites to switch to the classic editor…

Viewing 15 replies - 1 through 15 (of 22 total)

  • That actually changed at some point between v 1.0 and 1.3. I had it installed on a couple multi-sites, activated on a site-by-site basis, but then after an update, lost that ability.

    Hi @verdonv thanks for sharing that. So it id work well on a site by site basis or were there certain issues with it? If not, I’ll create a pull request on Github to revert it to previous behavior…

    @ravanh

    I didn’t get a lot of time to test it. I set CE plugin up in advance on 3 multi site installs, 2 large and 1 small. I updated the small one to WP 5 and did some tests. It seemed to be working OK but my testing was limited. In the 24 or so hours after that there were two releases to CE plugin. I then updated the two large multi sites to WP 5 and at that point released that the CE plugin behaviour had changed.

    In the end, my testing was light.

    @ravanh

    I think ultimately what you’re looking for now, in terms of control, should work. On the Network settings page you can allow admins to change the settings or not, and then on each site’s Writing Settings page, the site admin can define the default editor, and whether or not to allow users to be able to switch.

    Though I suppose what you cannot do is allow some site admins control over the settings, and others not.

    • This reply was modified 5 years, 11 months ago by verdonv.

    No, what I am looking for is to keep the new editor as default while allowing sites admins to revert to classic editor. This is not possible with the current Classic Editor forced to “network activate only” because that means the classic editor becomes default on all sites…

    @ravanh I believe in the recent updates they added options in the subsite’s settings, you should be able to toggle it from there whether that site uses the classic editor or the block editor. You will need to enable it fist at the bottom of /wp-admin/network/settings.php then Site Admins will be able to toggle it on and off under Settings > General or Settings > Writing on each subsite.

    I have to agree with the OP. There needs to be an option in the multi-site network settings to be able to set the default for all sites to either classic or block. It would then be up to the site admin to change as needed.

    Most of our sites would need to be touched after deploying this plugin to make the default block. In our test multi-site instance I have deployed this plugin after modifying the code, to the best of my ability, to set the default to block. We are currently testing to determine if the change is working.

    Thanks!

    I created this pull request, reverting the network wide only activation https://github.com/WordPress/classic-editor/pull/55

    As far as I can tell from the source code, it looks like an option to set the network wide default editor is planned (or at least possible) in a future release but until then, I suggest allowing site-by-site activation.

    Plugin Author Andrew Ozz

    (@azaozz)

    The option to disable the Block Editor by default on multisite and not allow site admins to do their own settings was added because of users requests here ??

    If the plugin is not “network activated” this won’t be possible.

    If you need more granular control which editor should be default for all sites, or want to control that on a site by site basis, there is a filter classic_editor_network_default_settings that can be used: https://github.com/WordPress/classic-editor/blob/master/classic-editor.php#L208. It will also let you set the “allow users” default.

    • This reply was modified 5 years, 11 months ago by Andrew Ozz.

    Hi @azaozz

    The option to disable the Block Editor by default on multisite and not allow site admins to do their own settings was added because of users requests here ??

    If the plugin is not “network activated” this won’t be possible.

    But that does not mean the plugin MUST be network activated at all times. It is perfectly possible to network activate a plugin that is not marked for “network wide only” activation.

    My pull request will allow super admin to decide for him/her self to:
    A. network activate the plugin and thus set the default editor to Classic on all sites (and optionally allow site admins to override this) or
    B. allow site-by-site plugin activation, effectively leaving the default editor to Block and allow site admins to revert to Classic.

    You see how forcing network activation prevents this last option?

    Please note that the pull request on Github allows site-by-site activation, while still also allowing network wide activation.

    @chaplina can you share what you changed to set the network default to block editor?

    Plugin Author Andrew Ozz

    (@azaozz)

    My pull request will allow super admin to decide…
    A. network activate the plugin and thus set the default editor to Classic on all sites (and optionally allow site admins to override this) or
    B. allow site-by-site plugin activation, effectively leaving the default editor to Block and allow site admins to revert to Classic.

    This is pretty much how it works now too. The only difference is that the site admins should change the options instead of (site) activating the plugin.
    – A is the default.
    – B is dependent on the site admins. They can choose “Block” as the site default editor and not allow users to change it. That virtually disables the plugin on their site. Also, there is the filter I mentioned above for more granular site-by-site control of the defaults.

    I wouldn’t mind removing the “network activation only” restriction, but we’ll need to find a good place to explain how the plugin will behave in both cases. Can perhaps add a == FAQ == section to the readme, still a bit worried most people won’t look there at all ??

    Plugin Author Andrew Ozz

    (@azaozz)

    Any suggestions for content for that == FAQ == section? ??

    First, much appreciation from me to the author for developing this plugin. WP should have at the very least included this as an option with the caveats that classic would get limited support (no new features) and would be “dropped” by v6.

    This plugin seems to break Divi (editing with Classic OK…editing with Block blank page with PHP error in logs). The ability to activate on a per-site basis would be splendid as our Divi sites will likely not care about the editor.

    diff below for changing default…apparently this can also be done via a filter but I’m not a WP expert so (FAQ hint :))

    --- classic-editor.php	2018-12-13 14:06:48.580319361 -0500
+++ classic-editor.php.ANDY	2018-12-13 11:07:21.582468527 -0500
@@ -188,7 +188,7 @@
 
 		if ( is_array( $settings ) ) {
 			return array(
-				'editor' => ( isset( $settings['editor'] ) && $settings['editor'] === 'block' ) ? 'block' : 'classic',
+				'editor' => ( isset( $settings['editor'] ) && $settings['editor'] === 'classic' ) ? 'classic' : 'block',
 				'allow-users' => ! empty( $settings['allow-users'] ),
 				'hide-settings-ui' => true,
 			);
@@ -200,7 +200,7 @@
 
 		if ( is_multisite() ) {
 			$defaults = array(
-				'editor' => 'classic',
+				'editor' => 'block',
 				'allow-users' => false,
 			);
Viewing 15 replies - 1 through 15 (of 22 total)
  • The topic ‘Multisite request’ is closed to new replies.