[buddypress-trac] [BuddyPress Trac] #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:  imath
     Type:  enhancement               |      Status:  assigned
 Priority:  high                      |   Milestone:  12.0.0
Component:  Route Parser              |     Version:
 Severity:  major                     |  Resolution:
 Keywords:  has-patch has-unit-tests  |
--------------------------------------+-----------------------

Comment (by prbot):

 ''This ticket was mentioned in
 [https://github.com/buddypress/buddypress/pull/84 PR #84] on
 [https://github.com/buddypress/buddypress/ buddypress/buddypress] by
 [https://profiles.wordpress.org/imath/ @imath].''
 Compared to commit [https://buddypress.trac.wordpress.org/changeset/13442
 13442], change the logic of Components user navigation generation by
 introducing a `BP_Component::register_nav()` function to globalize the nav
 items and make them available for the added URLs WP Admin settings screen.
 After a second thought, using `BP_Component::setup_nav()` to play the
 registration role can be problematic considering backward compatibility.
 We are maintaining `BP_Component::setup_nav()` to play the role of
 generating the user navigation, Third party plugins wishing their slugs to
 be customizable will need to "opt-in" BP Rewrites using
 `BP_Component::register_nav()`.

 This first version of the URLs WP Admin settings screen does not handle
 slug customization yet, it's used to make sure all BP Component user
 navigation slugs can be customized.

 Trac ticket: https://buddypress.trac.wordpress.org/ticket/4954

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