[buddypress-trac] [BuddyPress] #5212: Enable upgrade route for BP-Default for future BP releases

[buddypress-trac]

#5212: Enable upgrade route for BP-Default for future BP releases
--------------------------+------------------
 Reporter:  DJPaul        |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  2.0
Component:  Theme         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |
--------------------------+------------------

Comment (by r-a-y):

 > One thing we *could* do now is to bail out of registering the theme
 directory for anyone who is not currently running bp-default or a child
 theme. That would prevent new installations from switching to the EOL bp-
 default.

 I like this.

 > What'd be helpful (and here's a chance for non-devs to jump in) is to
 work up a list of the different scenarios where one would be using bp-
 default, or assets thereof, and to run a series of tests using DJPaul's
 patch. Things like: bp-default as active theme, as parent theme, plugins
 like Genesis Connect that pull assets from bp-default, etc.

 Here's some quick code to redirect assets from `/bp-themes/bp-default/` to
 `/themes/bp-default/`:
 http://pastebin.com/pSdxJsBv

 For this code to work, the `/bp-themes/bp-default/` asset must not exist
 and the `wp-content/themes/bp-default/` directory must exist.  It's better
 to do this in .htaccess, but thought I'd put up some initial code for now.

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