Could the classic widget plugin be part of the Classic editor plugin

Howdy @allan1978

Having them central was an idea initailly but it would become quite intricate and in the end it would become a dashboard of settings for all the WordPress opt out features. Also the name of that plugin is misleading, what if someone wants blocks in widget areas but not blocks in posts? Would they know that is the plugin? What about the other way around?

I now have to install and continually update another plugin on all of my clients sites.

These plugins could be easily managed via automatic updates as they have one clear purpose and have very trustworthy sources.

Also, for widgets at least and if you have the option to edit code, you can opt out without plugins via theme supports or filters?

Hey there @andraganescu

That all makes sense but you could change the plugin name to something more descriptive that covered its functionality. The classic editor plugin could then grow into a hub for disabling all block features.

I can enable auto updates but i’m still going to have to install a separate plugin just to disable block widgets which is a bit annoying when you have a large number of sites that will require it.

The option of the function is cool but again adding that in to each site would take about the same time as adding the plugin.

I read your point that manually opting out via a plugin might not be the way forward but there’s not really another option unless they add that to the core which will never happen.

Cheers,
Allan