Make WordPress Core

Opened 4 years ago

Last modified 4 years ago

#49398 new defect (bug)

Deactivating a widget can fail causing data loss

Reported by: lev0's profile lev0 Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 5.3.2
Component: Widgets Keywords: close
Focuses: administration Cc:


You cannot hide/toggle visibility of widgets. To stop one from showing on your site, you have to delete it which loses the widgets' content and settings. Surely this has been brought up before but I couldn't find a ticket. You can change posts' visibility without permanent deletion, why not widgets'? It seems like a large oversight.

Change History (4)

#1 @SergeyBiryukov
4 years ago

  • Component changed from Administration to Widgets
  • Focuses administration added
  • Keywords close added

Hi there, welcome to WordPress Trac! Thanks for the ticket.

You can hide a widget and keep its settings by moving it to the Inactive Widgets area, that's exactly what it is for.

Per WordPress Widgets support article:

If you want to remove the widget but save its setting for possible future use, just drag it into the Inactive Widgets area. You can add them back anytime from there. This is especially helpful when you switch to a theme with fewer or different widget areas.

#2 @lev0
4 years ago


But there is still a bug, dragging a widget out of a sidebar, but not down to the Inactive section which is off-screen, reveals the "Deactivate ..." text next to Aavailable Widgets, but releasing the mouse causes the widget to disappear, not actually be deactivated.

Last edited 4 years ago by lev0 (previous) (diff)

#3 @lev0
4 years ago

  • Summary changed from No way to temporarily disable a widget from admin UI, deletion & data loss is only way to remove one to Deactivating a widget can fail causing data loss

#4 @lev0
4 years ago

@SergeyBiryukov It would also be better if the "Delete" link on published widgets was instead "Deactivate", and the "Delete" link only showed on widgets in the inactive area.

Note: See TracTickets for help on using tickets.