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

[WordPress Trac]

#11817: Better Site Menu Management
-------------------------+--------------------------------------------------
 Reporter:  scribu       |        Owner:          
     Type:  enhancement  |       Status:  reopened
 Priority:  normal       |    Milestone:  3.0     
Component:  General      |      Version:          
 Severity:  normal       |   Resolution:          
 Keywords:  has-patch    |  
-------------------------+--------------------------------------------------

Comment(by nathanrice):

 Replying to [comment:331 ceenz]:
 > Each instance of nav_menu should have an id, name, array for items and
 array for options.
 > Each nav_menu_item should have an id, name, link, type, and array for
 options.
 >
 > That is seriously all that is required.

 I don't think that's true. For starters, the classes that get applied to
 menu items are heavily dependent on data relationships and pageview
 context.

 > All the BS surrounding custom post types different taxonomy (eg tag,
 categories) can be handled through an extend-able nav_menu class based on
 the nav_menu_item type and store the unique options for the type in the
 nav_menu_item options array.

 But why? If WordPress is going to offer menu management AND custom post-
 types and taxonomies, then why would the two not have some sort of
 "official" relationship?

 > I am really sorry but the whole situation is making me really angry.

 No kidding.

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