[buddypress-trac] [BuddyPress Trac] #6301: Group extension access settings disrespected by bp_core_new_subnav_item()
buddypress-trac
noreply at wordpress.org
Wed Mar 18 17:32:01 UTC 2015
#6301: Group extension access settings disrespected by bp_core_new_subnav_item()
--------------------------------+------------------------------
Reporter: dcavins | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Component - Groups | Version:
Severity: minor | Resolution:
Keywords: has-patch |
--------------------------------+------------------------------
Comment (by dcavins):
Yes.
I would also like it (a lot) if somewhere down the road we
simplified/unified the process of creating navigation in groups and member
profiles. Adding the ability to even reorganize navigation links (being
able to group several typically top-level navigation items under a new
navigation items is an obvious example--moving group invites into the
members tab, for instance) via filters would be pretty sweet. (I'm
thinking a bit of how when declaring a custom post type or taxonomy, you
can specify that it be added as a subnav item of an existing menu item.)
Separating the navigation link creation from the screen hook seems like a
good start. I'm surprised at how few times `bp_core_new_subnav_item()` is
called in the code; it's used once each in buddybar, component, groups-
classes and xprofile-loader.
Thanks for the feedback!
--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/6301#comment:3>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac
More information about the buddypress-trac
mailing list