[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     |
--------------------------+------------------
Changes (by boonebgorges):

 * milestone:  Awaiting Review => 2.0


Comment:

 Nice, this seems pretty well thought out. Thanks for starting the
 conversation here.

 Inevitably, there will be path issues - places where people hardcoded (or
 otherwise incorrectly) inferred the URL and file paths of assets, etc
 assumed to be in bp-default. I'm not sure there's much we can do about
 this technically, but it does suggest the requirement of having lots of
 warning and documentation for end users. I do *not* think there's time to
 do that for 1.9.

 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. Maybe a separate issue?

 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.

 Let's slate this for 2.0, and just get it done and over with :)

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