Support » Plugin: Classic Editor » Incorporate Classic Widgets

  • This plugin’s sole job is to disable Gutenberg. It has done that just fine for a while. But with the release today of WP 5.8, it was strange that a plugin intended to disable Gutenberg did not also disable the Gutenberg widget system. Even though a separate Classic Widgets plugin exists, why should that be needed if this plugin is already active?

Viewing 6 replies - 1 through 6 (of 6 total)
  • I have the very same thoughts. This plugin has 5M installs; 5M sites that just don’t want to work with block. Or 5M sites who are just “as it is”; like static sites. I have a bunch of them.

    WordPress should respect their choice in that, and when this plugin is installed; every encounter with blocks should be disabled by default. Or have the option to enable it.

    krzxsiek

    (@krzxsiek)

    Me too. I don’t want a disgusting block editor in widgets.
    Please add option to disable this.

    biziclop

    (@biziclop)

    See the relevant post here:

    Block-based Widgets Editor in WordPress 5.8

    Opting out of the block-based widgets editor

    The block-based widgets editor is enabled in WordPress 5.8 by default. There are several ways to restore the classic editor:

    A theme author may include remove_theme_support('widgets-block-editor'). Learn more:
    https://developer.wordpress.org/block-editor/how-to-guides/widgets/opting-out/#using-remove_theme_support

    A site administrator may use the new use_widgets_block_editor filter. Learn more:
    https://developer.wordpress.org/block-editor/how-to-guides/widgets/opting-out/#using-a-filter

    A user may install and activate the Classic Widgets plugin:
    https://wordpress.org/plugins/classic-widgets/

    BTW, this is the core of the plugin above:

    // 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' );
    • This reply was modified 6 months ago by biziclop.
    krzxsiek

    (@krzxsiek)

    @biziclop Very good info, thanks 🙂
    I will use this code in my themes and pages. 🙂

    Plugin Author Andrew Ozz

    (@azaozz)

    Not sure if it is a good idea to “merge” the functionality of the Classic Widgets plugin.

    • It is super simple to use.
    • As @biziclop mentions there are couple of other ways to switch to the classic widgets edit UI.

    In addition switching of the widgets editor can’t/shouldn’t be done on per user basis. It is a site-wide setting. Thinking that keeping it in a separate plugin would be better.

    If it’s super simple, that’s even one more reason to merge it in the Classic Editor plugin. As a default on option. I guess lot’s of site owners (5M installs) will be suprised when they enter the new widget area. Nobody can’t deny that working with blocks has it’s (steep) learning curves. So, this is an audience that has zero experience with blocks. An audience of 5 million.

    I knew there’s code and the Widget Plugin; but that is just “another plugin”. Even if it’s a few lines of code.

    By the way: i LOVE the block editor. I love it big time. But older custom projects who don’t want to switch, or don’t have the budget certainly after corona-times.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Incorporate Classic Widgets’ is closed to new replies.