Opens in a new tab
WordPress classic widgets

Disable the block-based Widgets screen. Bring back the classic editor.

Disable Block-Based Widget Screen restores the classic WordPress Widgets interface for themes that support it. Keep your existing widgets, review block-based items by area, and switch back whenever you need to.

  • Restore Appearance → Widgets to its classic interface.
  • Keep every existing widget and widget area intact.
  • See how many widgets are stored as blocks.
  • Reverse the change without converting data.
Classic WidgetsInterface preview
Appearance / WidgetsWidgets
Classic view
Main Sidebar3 widgets
Search
Navigation Menu
BlockSaved as a block
Existing block widgets stay in place and continue to display on the site.

Illustrative example, not a live WordPress settings panel.

Quick answer

What does Disable Block-Based Widget Screen do?

The disable_block_widgets module restores the classic editor at Appearance → Widgets for a theme that supports widgets. It applies the WordPress use_widgets_block_editor filter to return false, which also changes the Customizer’s Widgets panel. Your existing widgets are not converted or removed. The TheOneWP settings screen identifies widget areas and shows how many widgets are stored as blocks.

Why the interface changed

Simple sidebar changes should stay simple

Since WordPress 5.8, the Widgets screen can use the block editor even when the task is simply rearranging a search box, menu or text widget.

A different interface for familiar widgets

Classic widget workflows use dedicated widget panels and fields. The block-based screen uses a block canvas, which may not suit sites whose sidebars rely on long-established classic widgets.

Block-based widgets create a compatibility question

A widget created in the block editor is still a widget, but it is stored as a block. When the classic screen is restored, it appears as a widget named Block, not as the same visual block editor.

Some themes have no Widgets screen to restore

Block themes normally manage these parts of the site in templates rather than traditional widget areas. A reliable setting needs to identify that limitation before a switch is used.

A focused WordPress solution

The classic Widgets screen, without a content migration

Enable one module to change the editor WordPress displays. The widgets already stored in your site stay where they are.

Restore a familiar screen

Use the classic widget administration screen for themes with traditional widget areas.

Preserve saved widget data

No data conversion, copying or deletion. Your widget assignments remain intact.

Easy to reverse

Turn the module off to let WordPress and your other active software determine the widgets interface again.

Verified feature set

A small module with useful context

The settings switch is intentionally simple; the accompanying information is read from your active theme and saved widget assignments.

Customizer

Same choice in both places

The Widgets panel in the Customizer follows the same WordPress decision; no separate option is needed.

Widgets panelOne filter
Inspection

Widget-area inventory

Lists widget areas registered by the active theme and counts the widgets assigned to each area.

Widget areasCurrent theme
Block awareness

Identifies saved block widgets

Counts widgets whose stored IDs begin with block-, both for individual areas and overall.

Block countsArea details
Clear notices

Explains when nothing changes

Reports when the theme has no Widgets screen, when areas are empty, or when a classic interface is already active.

Theme supportExisting classic UI
Reversible

Stored widgets stay untouched

The interface switch does not rewrite the sidebars_widgets option, edit widget content or permanently convert blocks.

No conversionSwitch off anytime
Practical use cases

When classic widgets make more sense

For sites that still work with traditional widget areas, the right editing screen can simplify routine maintenance.

Maintaining an established sidebar

Keep working with familiar widgets for search, navigation, and text instead of adapting an unchanged layout to the block canvas.

Handing over a client website

Offer a consistent, straightforward widget-editing workflow for site managers accustomed to the traditional WordPress dashboard.

Checking a site before switching

Read the area-by-area block-widget counts before deciding whether the classic editor fits your current widget content.

What changes and what does not

An interface decision, not a rebuild

The module changes how WordPress lets administrators manage widgets, without editing the underlying widget data.

Changed: the Widgets editorWhere supported, Appearance → Widgets uses the classic interface instead of the block canvas.
Changed: the Customizer panelWidget controls in the Customizer follow the same classic-versus-block choice.
Unchanged: saved widget contentWidget data, positions and assigned sidebar areas are not migrated or deleted by this module.
Unchanged: post and page editorsThis toggle does not switch the editor used for posts or pages; that is handled separately.
Technical footprint

One WordPress filter, no scanning loop

The frontend-facing feature is the interface choice itself, not a background task or content-processing pipeline.

Single selection filter

When enabled, the module registers one use_widgets_block_editor callback. Its return value is simply false.

Counts only for the settings view

The settings renderer reads registered widget areas and their stored assignments to explain how the module will behave on this site.

No invented speed claims

The implementation does not provide a measured performance improvement for the frontend. Its benefit is administrative workflow simplicity.

Scope and safety

A narrow change with no widget rewriting

The supplied module has no custom remote requests, data migrations or AJAX endpoints for this feature.

01

Uses a documented WordPress filter

The module uses use_widgets_block_editor rather than patching WordPress core files or replacing the widget data model.

02

Does not change permissions

Widget editing remains governed by WordPress and the current user’s existing permissions. The module does not create a new role or capability system.

03

Does not delete widgets

The filter chooses an interface; it does not alter the existing sidebars_widgets assignments or widget settings.

04

Reports site-specific limitations

The settings panel identifies unsupported themes and existing classic-screen behavior instead of implying that the switch always changes a visible screen.

Compatibility and limitations

Know when the switch can actually help

The module respects how the active WordPress theme exposes widget areas and how WordPress stores block widgets.

Block themes

No traditional Widgets screen to restore

Many block themes work through site templates instead. The module explains when the theme has no widgets screen and the switch changes nothing.

Theme-dependentNo false promise
Stored blocks

Block widgets still display

A block-based widget shows as a widget named Block in the classic editor. It still renders, but it is not visually editable there as a block.

block-* IDsSaved markup
Solution comparison

TheOneWP and other widget workflows

The key distinction is which editor you use, not a different set of widgets or a performance guarantee.

AspectTheOneWP module enabledWordPress / other approaches
What changes? The Widgets screen and Customizer widget editorMay offer block widgets, classic widgets, or a mix based on current configuration
Existing widget data Preserved; no conversion or migrationPreserved when an editor choice is changed without migration
Block widgets on classic screen Displayed as Block widgets with saved markupA block editor provides visual block controls when available
Theme without widget support Panel explains there is no Widgets screen to restoreAvailability still depends on theme widget support
Extra configuration One toggle plus read-only, site-specific widget countsOther approaches may involve a theme option, separate plugin or code filter
Recommended workflow

Restore classic widgets in four clear steps

Check the theme and existing block widgets, then use the interface that best fits the site.

01

Open the module settings

In TheOneWP settings, find Disable Block-Based Widget Screen in the Components area.

02

Review the site-specific notes

Check whether your theme has a Widgets screen, whether another component already forces the classic view, and how many widgets are stored as blocks.

03

Enable the module

Switch the module on and save your settings. The change selects the classic Widgets interface; no widgets are converted.

04

Verify and reverse if needed

Open Appearance → Widgets where the theme supports it. If block-based items need visual editing, turn the module off and return to the block interface.

Best practices

Switch interfaces with the content in mind

A few checks make the change predictable for anyone maintaining the site.

01

Read the block-widget counts first

If an area contains block-based widgets, the classic screen will show them as Block widgets. Plan to use the block editor again when you need visual changes to those blocks.

02

Verify the active theme supports widgets

If TheOneWP reports that no Widgets screen exists, enabling the switch cannot create one in a block theme.

03

Check for another classic-widgets setting

If a theme or another plugin already returns the classic Widgets screen, the toggle may appear to do nothing. The panel reports that situation.

04

Keep this separate from post editor choices

Use the separate Disable Gutenberg settings when the goal is to change the editor for posts and pages, rather than the Widgets screen.

Common mistakes

Avoid the three usual assumptions

Restoring the classic screen is straightforward once its boundaries are understood.

Thinking this converts block widgets

It only changes the editing interface. Block widgets remain blocks and appear as Block widgets in the classic screen.

Expecting a Widgets screen in every theme

Many block themes do not provide the traditional widget screen at all. The module cannot add one to a theme that does not support it.

Assuming posts and pages also change

The editor for post content is independent of the widgets editor. Use the dedicated Gutenberg controls if that is the actual goal.

Frequently asked questions

Disable Block-Based Widget Screen FAQ

Answers reflect the module’s class, its settings renderer, and WordPress’ existing widget-editor filter.

What does Disable Block-Based Widget Screen do?

It replaces the block-based Appearance → Widgets interface with the classic widgets screen on themes that support widgets. The change also applies to the Widgets panel in the Customizer.

Does this delete or convert my existing widgets?

No. The module changes which editing interface WordPress uses. It does not convert, delete, move or rewrite stored widgets.

What happens to widgets that were created as blocks?

They stay in their existing widget areas and continue rendering. In the classic interface they appear as widgets named Block, with their saved markup shown in a plain field rather than the visual block editor.

Can I still edit block widgets in the classic screen?

Not with the same visual block controls. Switch back to the block-based Widgets screen if you need to edit existing block widgets using the block interface.

Will the module disable the block editor for posts and pages?

No. This module only changes the widgets editing interface. The separate Disable Gutenberg module controls the editor for content types.

Will my site look different to visitors?

The module does not directly change frontend widget rendering or layout. Existing widgets and their assigned areas remain unchanged; their edit screen is what changes.

Does it work with WordPress block themes?

Only when the active theme supports the traditional widgets screen. Most block themes do not, because they place equivalent content in block templates instead.

How do I know if my theme has block widgets?

The TheOneWP settings panel counts widgets in the widget areas registered by the current theme and identifies how many of them are saved as blocks.

Why does enabling it sometimes make no visible difference?

The current theme may not support widgets, the widget areas may be empty, or the theme or another plugin may already be using the classic screen. The module panel reports these conditions.

Does this affect the WordPress Customizer?

Yes. WordPress uses the same block-editor availability decision for the Widgets screen and the Customizer’s widgets panel.

Is there a per-user or per-role setting?

No. The supplied module has one enable/disable setting and does not offer separate roles, users or individual widget-area controls.

How do I restore the block-based Widgets screen?

Turn the Disable Block-Based Widget Screen module off. If your theme supports block widgets and no other code or plugin forces the classic screen, WordPress will use the block interface again.

Keep the widgets you have.Choose the editor you prefer.

Restore the classic WordPress Widgets screen with a reversible switch, backed by clear information about your site’s widget areas and existing block widgets.