[buddypress-trac] [BuddyPress Trac] #6001: BP_MEMBERS_SLUG should be used in the groups/groupname/members slug (was: BP_MEMBERS_SLUG should be used in groups)

[buddypress-trac]

#6001: BP_MEMBERS_SLUG should be used in the groups/groupname/members slug
-------------------------+-----------------------------
 Reporter:  slaFFik      |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  low          |   Milestone:  Future Release
Component:  Groups       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+-----------------------------
Changes (by DJPaul):

 * priority:  normal => low
 * type:  defect (bug) => enhancement
 * milestone:  Awaiting Review => Future Release


Comment:

 The "members" part of this slug is inside what we call a component's sub-
 navigation. Visually, it's displayed in a separate block from a
 component's main navigation.

 I am pretty sure that no part of any component's sub-navigation items are
 currently able to have its slug customised without hacking core in
 multiple places. The fact that "members" also happens to be the slug of
 another BP component is an unforunate and confusing coincidence.

 I don't think we plan to address this until, in some future release, we
 use WP rewrite rules to handle URL routing for this, and update/change
 everything in one go.

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/6001#comment:2>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac