Make WordPress Core

Opened 5 years ago

Last modified 5 years ago

#23716 closed defect (bug)

Discuss theme locations as meta box vs. checkboxes — at Initial Version

Reported by: lessbloat Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Menus Keywords: 3.6-menus
Focuses: Cc:


Relocating a side topic discussion that started on the make/ui P2, and then moved to the wrong ticket.

To summarize chips last post (and kick us off here), here are the concerns Chip would like to address:

1) When assigning pre-defined custom menus to a Theme's defined Theme Locations, the process now requires considerably more steps, clicks, page refreshes, and time

2) When looking at the "Select a menu" dropdown, there is no way to determine if all Theme locations have an associated custom menu assigned

3) When editing a given menu, in the Theme Location field checkboxes, there is no indication that a given Theme Location already has a custom menu assigned to it

4) With long-ish custom menus, the "Theme Locations" field is buried "beneath the fold", resulting in no initially visible UI for assigning the current menu to a Theme Location

5) Overall, the page now seems to emphasize adding/editing custom menus, and seems to deemphasize assigning custom menus to Theme Locations, and the latter is arguably the more important role/task for Appearance -> Menus

Change History (0)

Note: See TracTickets for help on using tickets.