[wp-trac] [WordPress Trac] #13337: Menu item order isn't saved automatically (was: Menu order isn't saved when adding a home link)

WordPress Trac wp-trac at lists.automattic.com
Tue May 11 13:10:48 UTC 2010


#13337: Menu item order isn't saved automatically
-------------------------------+--------------------------------------------
 Reporter:  Denis-de-Bernardy  |       Owner:     
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  3.0
Component:  Menus              |     Version:  3.0
 Severity:  normal             |    Keywords:     
-------------------------------+--------------------------------------------

Comment(by koopersmith):

 A lot of these problems tie into the draft menu item system: We have a
 draft state for menu items, but not a draft state for the menu as a whole.
 As a result, when a menu item is added (but not saved) it will be in a
 draft state (and appear on the backend, but not the frontend). When a menu
 is rearranged, however, the new positions cannot be saved until the user
 clicks "Save Menu". Auto-saving positions isn't feasible because saving
 the positions to the db causes the published menu items to rearrange on
 the frontend (not to mention the massive number of ajax requests it would
 require).

 The smaller bug is that the JS should always update the menu item position
 data before the menu is saved (and only before the menu is saved, as
 that's the only time position data can be saved to the db anyway). A patch
 is attached to fix that.

 We've planned to add an "unsaved" label to draft menu items to clear up
 some of the UX issues here. As for a solution to the first problem, I'd
 say that we should give draft menu items a position of -1 and
 automatically place them at the end of the menu.

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


More information about the wp-trac mailing list