[wp-trac] [WordPress Trac] #26946: Decouple the Menu System from Posts and Taxonomies
WordPress Trac
noreply at wordpress.org
Sun Jan 26 18:47:51 UTC 2014
#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):
Replying to [comment:6 nacin]:
> Being involved in building menus in 3.0 probably subtracted a few years
from my life.
I can believe it. :)
> Anyway — the primary reason you've proposed for doing this is that
custom taxonomies share term objects.
To be clear, that was not the primary reason. That issue was the one that
got me to post this ticket and it provided a reason I thought core might
get behind since it affects users. 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.
> So, in the end, this is a non-starter for two reasons:
Fine. I just wish time was allowed for others to voice their opinions and
discuss options for potential implementation before deciding this, or
deciding other things, are not a good idea. The ''"We know better so
there's no need for discussion"'' approach can seriously demotivate people
who want to contribute,
[https://twitter.com/curtismchale/status/427502670060863489 people other
than just me].
--
Ticket URL: <https://core.trac.wordpress.org/ticket/26946#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list