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

[buddypress-trac]

#4954: Migrate BP's custom URI parser to use WP's Rewrite API
---------------------------+-----------------------------
 Reporter:  boonebgorges   |      Owner:  johnjamesjacoby
     Type:  task           |     Status:  new
 Priority:  high           |  Milestone:  1.8
Component:  Rewrite Rules  |    Version:
 Severity:  major          |   Keywords:
---------------------------+-----------------------------
 BP's custom URI parser (living mostly in `bp_core_set_uri_globals()`) is
 slow, error-prone, non-extensible, non-testable, and out of step with WP
 best practices. This ticket is a master ticket for the task of migrating
 from our current URI parser to the WordPress Rewrite API.

 JJJ will be leading this task. Here's an outline of what will need to be
 covered, which I'm sure he and others will improve:

 - Port some of the basic rewrite architecture from somewhere like bbPress
 - Generalize some of the logic, to account for BP's system of
 current_component, current_action, action_variables
 - Ensure backward compatibility with plugins that add arbitrary sub-paths
 to BP addresses, whether it be via BP_Group_Extension, BP_Component, or
 manual detection of $bp->current_component etc
 - Add administation pages for the manual modification of slugs (see eg
 #2086)
 - Maintain backward compatibility with slugs set via constant (eg
 `BP_GROUPS_SLUG`)
 - Develop a tool for automatic migration from bp-pages to new slug system.
 In addition to the rewrite rules themselves, migration tool should be
 sensitive to Menus that include reference to bp-pages
 - Unit tests as appropriate

 There is a fairly large number of tickets, both in and out of the 1.8
 milestone, that will become irrelevant after the bp-pages schema has been
 abandoned. (Some will not necessarily be irrelevant, but they will require
 a totally different approach, and so should not be addressed until after
 the rewrite stuff is at least basically in place.) For the moment, I'm
 leaving those tickets open, in case the rewrite stuff were to take more
 than one dev cycle. An incomplete list from the 1.8 milestone: #2086 #4367
 #4630 #4726 #4882 #4884 #4913 #4917 #3998

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/4954>
BuddyPress <http://buddypress.org/>
BuddyPress