[wp-trac] [WordPress Trac] #26946: Decouple the Menu System from Posts and Taxonomies

[WordPress Trac]

#26946: Decouple the Menu System from Posts and Taxonomies
--------------------------------------------------+----------------------
 Reporter:  MikeSchinkel                          |       Owner:
     Type:  enhancement                           |      Status:  closed
 Priority:  normal                                |   Milestone:
Component:  Menus                                 |     Version:  trunk
 Severity:  normal                                |  Resolution:  wontfix
 Keywords:  needs-patch dev-feedback 2nd-opinion  |     Focuses:
--------------------------------------------------+----------------------

Comment (by MikeSchinkel):

 > How is cache or options different from what I described as log?
 (rhetorical question)

 If in your mind they are not different then for the purposes of this
 discussion they are the same.  I don't have a need to make the distinction
 if you don't.

 > I'm talking about structural changes of the menu system itself. For e.g.
 properties of menu items are changed with an update of WP core.

 Other than the ability to write directly to the tables w/o using the
 WordPress API I'm pretty sure it could all be made compatible, both for
 SQL read and for any other interactions ''(except SQL update or insert.)''

 > Seriously. Else it'd be name options and other stuff, right?

 I don't think there is such a thing as a definition of ''"options"'' such
 that would disallow storing something that needs to be global.

 We'll just have to agree to disagree on this one.

 > Yes, currently people are using it as if it would be name crap and more
 crap, but I wouldn't set goals that low.

 Yes, the current ones are the core committers. :)

 > I was afraid you would.

 Sorry, twas your example.  :)

 I think maybe your response to the idea was a gut-level ''"no"'' which if
 so means you making an assumption that this proposal ''(would have)''
 caused problems but you can't put your finger on any specific example? It
 feels like you can only find principles which you think apply and I think
 don't apply? ''(I'm not criticizing; I've been in the situation where I
 felt a change was wrong but couldn't put my finger on it either.)''

 FWIW, I've been thinking about this for over a year and I've yet to find a
 use-case where storing as serialized data would cause a problem.  Which is
 a moot point related to core, it seems.

 > Users are shared across multisites.

 `usermeta` would be the place to store user-specific menu options.

 No harm, no foul.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/26946#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform