[buddypress-trac] [BuddyPress] #2086: Some slugs need to be changeable, add language strings.

[buddypress-trac at lists.automattic.com]

#2086: Some slugs need to be changeable, add language strings.
--------------------------+------------------
 Reporter:  sulley        |       Owner:
     Type:  enhancement   |      Status:  new
 Priority:  major         |   Milestone:  1.6
Component:  Core          |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |
--------------------------+------------------
Changes (by boonebgorges):

 * milestone:  Future Release => 1.6


Comment:

 I would personally like to get this taken care of. It will be tedious, but
 easy, props for someone. It doesn't even have to be done all at once -
 patches taking care of single slugs would be fine.

 Suggested strategy for maximum flexibility: Build template tags that
 conditionally define a constant, and then echo and return a filtered
 version of the constant. Eg:


 {{{
 function bp_messages_compose_slug() {
   echo bp_messages_get_compose_slug();
 }
   function bp_messages_get_compose_slug() {
     if ( !defined( 'BP_MESSAGES_COMPOSE_SLUG' ) ) {
       define( 'BP_MESSAGES_COMPOSE_SLUG', 'compose' );
     }

     return apply_filters( 'bp_messages_get_compose_slug',
 BP_MESSAGES_COMPOSE_SLUG );
   }

 }}}

 The bit where you define the constants is probably not strictly required
 (could just use a filter) but we do it with other slugs so we could
 probably stick to the strategy for ease of documentation. Then, comb
 through, find the hardcoded references, and replace as necessary.

 I'm going to move back to the 1.6 so that people can easily see the ticket
 and contribute if they want some Mad Props during this dev cycle, with the
 understanding that we can and should punt if no one patches.

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/2086#comment:8>
BuddyPress <http://buddypress.org/>
BuddyPress