[buddypress-trac] [BuddyPress Trac] #7116: Move asset template parts away from bp-legacy

buddypress-trac noreply at wordpress.org
Mon Oct 10 10:46:55 UTC 2016

#7116: Move asset template parts away from bp-legacy
 Reporter:  r-a-y                        |       Owner:
     Type:  enhancement                  |      Status:  new
 Priority:  normal                       |   Milestone:  Awaiting Review
Component:  Templates                    |     Version:
 Severity:  normal                       |  Resolution:
 Keywords:  has-patch 2nd-opinion close  |

Comment (by DJPaul):

 That argument could apply to any front-end feature we add, including (for
 example) an entire new Component. We'd then end up with Components
 templates in some other folder. I'm not sure the comparison with WordPress
 is perfect (different scale; different intended target audience), but I
 understand what you're saying.

 I imagine we will have some variable in the future that says what the
 "default" template pack is (for new installs). For these "features" that
 we add that have template parts, could we make it so that if the file
 wasn't found in the template stack, to fall-back to the "default" template
 pack directory?

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/7116#comment:9>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac

More information about the buddypress-trac mailing list