WordPress.org

Make WordPress Core

Opened 2 years ago

Last modified 15 months ago

#35132 new enhancement

UX improvements when creating/editing menus

Reported by: chris_dac Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 4.4
Component: Menus Keywords: needs-patch
Focuses: ui, administration Cc:

Description

Using the menus component (accessible via Appearance -> Menus) is currently a bit of a pain! A few improvements would go a long way to making this feature more pleasant to use:

  1. When editing a menu, the Pages/Posts/Custom Links/Categories panel on the left hand side does not show which pages have already been added to the menu; all items are unchecked, even if they've already been added to the menu. This makes it very hard to discover any new pages which need adding and also makes it easy to accidentally add duplicate pages.
  1. There is currently no means to bulk edit existing menu items - two functions which would be very useful here are the deletion of all existing items and the alphabetical sorting of all existing items.
  1. It should be possible to select all children of an existing parent page. For example, if creating a sub menu that lists 20 children of a parent page, we have to click on each child separately. If a new page is added a week later, then items 1 and 2 above become problematic - we need to either carefully check for the new page in the list on the left, cross referencing that list with the existing pages, or we have to delete everything in the menu and add each individual item again from scratch, which despite being quite lengthy is actually the quickest, least error-prone option here.

Hope this helps!

Change History (1)

#1 @welcher
15 months ago

  • Keywords needs-patch added

Thanks for the ticket!

These are some great ideas, I think that while the second two may be better addressed with plugins, being able to see immediately what has already been added to a menu would be very helpful.

Want to add some screenshots of what you are envisioning or perhaps try a patch?

Related 31218

Note: See TracTickets for help on using tickets.