[buddypress-trac] [BuddyPress Trac] #3745: Change BP Group Forum and Member slugs-name like bp docs can

buddypress-trac noreply at wordpress.org
Mon Nov 5 02:06:54 UTC 2018

#3745: Change BP Group Forum and Member slugs-name like bp docs can
 Reporter:  johnnymestizo               |       Owner:  johnjamesjacoby
     Type:  task                        |      Status:  assigned
 Priority:  normal                      |   Milestone:  Under Consideration
Component:  Forums                      |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  trac-tidy-2018 2nd-opinion  |
Changes (by johnjamesjacoby):

 * keywords:  trac-tidy-2018 => trac-tidy-2018 2nd-opinion
 * owner:  lookingahead => johnjamesjacoby
 * milestone:  4.0 => Under Consideration


 Re: forum slugs, this is fixed in bbPress for what will be 2.6:

 Someone wanting to update the slugs would use a small plugin. Something
 add_action( 'bbp_buddypress_groups_loaded', function( $forum_groups ) {
     $forum_groups->slug       = 'channel';
     $forum_groups->topic_slug = 'chat';
     $forum_groups->reply_slug = 'chit';
 } );


 Re: other group slugs, the issue remains that these slugs are not easily
 changed, as they are critical to the functionality of BuddyPress groups,
 and there is no code in place to allow them to be aliased or localized.

 7 years without discussion kinda proves this isn't something worth
 prioritizing, so the one and only way I see this being at all urgent is
 strictly in relation to localization. Like @lookingahead said above,
 having these be hard-coded to English isn't ideal.

 Technically speaking, this isn't a particularly easy change, because the
 slugs for most actions, and action-variables are assumed to be what they
 are everywhere throughout the codebase.

 Functions like `bp_get_group_current_admin_tab()` internally assume that
 `admin` is the action slug. This is not dissimilar from WordPress assuming
 that `wp-admin` is the admin path, but personally, I don't think that's
 very great either.


 This issue is equal parts ancient and challenging. It's unlikely to be
 resolved without a significant rethink of how to identify slug-to-template
 relationships, likely with some unique ID (which is what we did with
 components originally.)

 In that case, I'd motion that we either close this issue and make a new
 one specifically for a complete slug overhaul, or we throw a bunch more
 slug constants at the problem if we aren't interested in that level of

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/3745#comment:13>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac

More information about the buddypress-trac mailing list