[wp-trac] [WordPress Trac] #11817: Better Site Menu Management

[WordPress Trac]

#11817: Better Site Menu Management
----------------------------+-----------------------------------------------
 Reporter:  scribu          |       Owner:  scribu   
     Type:  task (blessed)  |      Status:  accepted 
 Priority:  normal          |   Milestone:  3.0      
Component:  General         |     Version:           
 Severity:  normal          |    Keywords:  has-patch
----------------------------+-----------------------------------------------

Comment(by cognitions):

 2.      In addition, referencing the ongoing concern about multilevel
 menus:
 I believe it may unnecessary to clutter the widget with hierarchical
 options.
 When a user first adds a new Page or Category ( or Term of a custom
 hierarchical Taxonomy), the parent/child relationship is then defined and
 registered.
 In the new Menu Management System, I propose that:
 If a user includes both a child and its parent in a menu instance, then
 the pre-existing hierarchy should be preserved and spat out in the html
 with relevant <ul> <li>. If the user includes a child without its parent,
 that menu item should be treated as top level menu item, even though it is
 defined as a Child when first registered. This avoids the need to add a
 second tier of hierarchical levels.

 I courteously disagree with Ryan. I think dynamic suggestions in this
 context would be frustrating and compromise usability. Previous popularity
 of an item is not logically related to current intent.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/11817#comment:81>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software