[buddypress-trac] [BuddyPress Trac] #4954: Migrate BP's custom URI parser to use WP's Rewrite API

buddypress-trac noreply at wordpress.org
Sat Feb 15 18:25:05 UTC 2014

#4954: Migrate BP's custom URI parser to use WP's Rewrite API
 Reporter:  boonebgorges   |       Owner:  johnjamesjacoby
     Type:  task           |      Status:  new
 Priority:  high           |   Milestone:  2.0
Component:  Rewrite Rules  |     Version:
 Severity:  major          |  Resolution:
 Keywords:                 |

Comment (by johnjamesjacoby):

 One thought after applying this and stepping through it, I'm worried it's
 more invasive to the existing URI router than what I had imagined. I'm
 thinking we should be able to bolt the rewrite rules on top of the
 existing functionality, and de-prioritize the old URI router similar to
 the way we did with theme compatibility. That way (if I'm thinking about
 this correctly) any old third-party components without rewrite rules will
 still continue to function the same way they always have, with the URI
 router still catching them appropriately.

 Thoughts on renaming `bp_path` to `bp_action` to retain the existing
 component/action/variables naming and relationships we're so used to now?
 Or, rather than having BuddyPress act as a central router again (with
 standard component/path/action vars) if maybe they should always be
 unique. Something like:

 * `bp_directory=bp_members` = Members Directory
 * `bp_member_id=1` = Member Profile for User ID 1

 We also should stick to using WordPress's wrappers instead of combining
 the rewrite rules array. Something like what bbPress does now would be
 best, though we may even want to have our own wrappers for easily
 registering component/action/variable style pages. See:


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

More information about the buddypress-trac mailing list