[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 F J Kaiser):

 Replying to [comment:6 nacin]:
 > That said, I don't think the schema is the problem.

 I agree with you here. The idea of using Taxonomies and CPTs IMO is a good
 one. Provides enough flexibility and gives low end devs enough public
 API/Template Tags, etc./tools to interact with it.

 Replying to [comment:7 MikeSchinkel]:
 > My primary reason is to make menus less fragile in plugins and themes,
 especially when one is trying to add custom functionality. and the
 secondary reason is to remove unintended consequences for when doing
 things that inadvertently affect menus, albeit a distant second.

 Switching to something else doesn't fix the underlying problem. CPTs and
 Taxonomies need some care: true. But we shouldn't just switch and start to
 build and maintain yet another system. IMHO '''everything''' in WP should
 rely on CPTs and Taxonomies - even admin pages and the admin menu. The
 more we build on CPTS & CTs, the better we can focus on it, the better WP
 gets as there're less things pulling off resources. And I'm hardly against
 serialized arrays and even more against serialized arrays in tables and
 completely against stuffing menu items in the objects table. I hope I
 don't need to, but I'm able to elaborate that in detail.

 Replying to [comment:6 nacin]:
 > I think we were just using custom post types and custom taxonomies for
 the first time and did it the "long way". It ended up being over-
 engineered in nearly every way, and it could benefit from a lot of TLC on
 the internals.

 Very true, that. But to be honest: It doesn't only need "love on the
 internals". It should be rewritten from scratch. No one can fix '''that'''
 mess. Stating that as I thought I could fix it this weekend and provide a
 patch. (Yes, I'm aware of the times when it was written and the PHP
 version it was written in).

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