[buddypress-trac] [BuddyPress Trac] #7157: UI to pick Template Packs

[buddypress-trac]

#7157: UI to pick Template Packs
------------------------------------+------------------
 Reporter:  DJPaul                  |       Owner:
     Type:  defect (bug)            |      Status:  new
 Priority:  strategic               |   Milestone:  2.7
Component:  Administration          |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |
------------------------------------+------------------

Comment (by imath):

 Thanks for your feedbacks.

 7157.02.patch is:
 - removing the upload/delete part of the patch.
 - simply listing BP Legacy and the active plugins who registered a theme
 package using the existing `bp_register_theme_package()` function.
 - keeping the "Preview" and "Customize" buttons.

 > But I think it's overkill, and not very transparent for third-party
 developers
 The developer can use any location of his choice as soon as he respects
 this organisation:
 {{{
 /anyrandomname
    /buddypress
    /css
    /js
    buddypress-functions.php
 }}}

 > what should happen? This is related to the question that @Offereins asks
 above.

 I don't know about "should". But Theme designers can eventually:
 - build a Standalone BuddyPress theme using `add_theme_support(
 'buddypress' )`. Just like BP Default.
 - Force `bp_get_theme_compat_id()` to return 'legacy'

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