Support » Plugin: Classic Editor » Add support to disable Widget Block Editor 5.8

  • Hey team,

    With the release of WordPress 5.8, can you please look into adding the support to also disable the new Widget Block Editor? I know you have a separate plugin, but I think it would be a appropriate the add the support here as well. Anything we can do to limit the amount of plugins to install and manage would be helpful.

    Best regards,

Viewing 9 replies - 1 through 9 (of 9 total)
  • I was also hoping for this! It makes sense that sites using this plugin would also want to exclude the widget blocks – or at least have the option to, for the cleanest experience.

    @wpcodeus According to the release notes, there is a way to opt-out manually, if you don’t want to add a plugin to do it. But I completely agree, it would be a much more hassle-free and buttoned-up solution to have it integrated with this plugin. Don’t see any reason why they can’t have both plugins with some overlapping options depending on the need of the site.

    Thread Starter WP Codeus

    (@wpcodeus)

    @slouchyflower,

    I am glad to hear I am not the only one who thinks this makes sense.

    WordPress did include some filters to disable the Widget Block Editor with a few lines of code. I will include it to this thread incase someone is looking for them:

    // Disables the block editor from managing widgets in the Gutenberg plugin.
    add_filter( 'gutenberg_use_widgets_block_editor', '__return_false' );
    
    // Disables the block editor from managing widgets.
    add_filter( 'use_widgets_block_editor', '__return_false' );

    However, this is one extra step that is needed when building out new WordPress installs. A few minutes saved here and there add up fast haha

    Yeah, it’s way cleaner to only have to remember to remove a single plugin to restore stock functionality in the future, too. As opposed to: remove a plugin and remove a bunch of lines from functions.php too.

    I saw this comment on the release page and it’s giving me some flashbacks to when the plain text widgets automatically converted to formatted text widgets and messing up code: https://make.wordpress.org/core/2021/06/29/block-based-widgets-editor-in-wordpress-5-8/#comment-41551 Hopefully this will get ironed out soon. I’m going to have to do some testing of both methods and see what shakes out with this plugin.

    It would be very nice to know their plans ASAP. Whether they plan on adding that option to this plugin, so we can at least get started doing whatever we need to do. 🙂

    Plugin Author Andrew Ozz

    (@azaozz)

    Not sure it would be good to “merge” the Classic Widgets plugin. See https://wordpress.org/support/topic/incorporate-classic-widgets/#post-14686835.

    Thread Starter WP Codeus

    (@wpcodeus)

    @azaozz Clearly there is a large percentage of people who prefer to not deal with Gutenberg with this plugin having over 5 million downloads.

    The new Widget Block Editor uses the same design and components as Gutenberg.

    Other plugins that are similar have already introduced this option which you can view here: https://wordpress.org/plugins/disable-gutenberg/

    I guess we will just need to switch for all our installs…

    Plugin Author Andrew Ozz

    (@azaozz)

    Widget Block Editor uses the same design and components as Gutenberg

    @wpcodeus Right, but don’t think the underlying technology is the “problem” here. Using blocks instead of widgets in the “widget areas” makes them a lot more useful and adds a lot more options and possibilities.

    Of course there will probably be some old plugins conflicts, etc. Having a separate, very easy to use plugin to revert back to the old widgets editing UI seems better and easier to manage. I don’t see a good reason to lump the two plugins together. Not a better UX imho.

    • This reply was modified 2 months, 3 weeks ago by Andrew Ozz.

    I’m also surprised to see this wasn’t rolled into Classic Editor. It seems to me that anyone with Classic Editor installed would prefer not to use the Block Editor.

    @azaozz I’m not advocating for merging the two and forcing everyone to use the same plugin, for the record. For those who just want the widgets restored, they can use the standalone plugin.

    I don’t see any issue with also adding that option in the Classic Editor plugin, since there’s likely a lot of crossover with those folks already using it. To your point about it being site-wide vs user-based, it would seem sufficient to have a warning next to the setting that says it’s a site-wide change for all users. I’m sure there will be people complaining on both sides, but this feature seems in line with the intent of the Classic Editor plugin as people are using it. And if people do want to use the block widgets alongside the classic editor, they could just leave the classic widgets setting off. Thanks for considering!

    Plugin Author Andrew Ozz

    (@azaozz)

    it would seem sufficient to have a warning next to the setting that says it’s a site-wide change for all users

    There was actually a PR to add something like this to the Classic Editor plugin. After some tests and discussions it became apparent that using a separate plugin would be better and easier for the users. Main reason is that Classic Editor is mostly targeted at switching between the editors on the Edit Post screen, and admins enabling or disabling it. Classic Widgets is much simpler and is mostly targeted at keeping old plugins that do unexpected and/or “hacky” things with widgets still working.

    • This reply was modified 2 months, 3 weeks ago by Andrew Ozz.
Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.