[buddypress-trac] [BuddyPress] #4855: Method to override a plugins use of plugins.php or add filters to bp_template_title and bp_template_content
buddypress-trac
noreply at wordpress.org
Wed Mar 6 06:04:20 UTC 2013
#4855: Method to override a plugins use of plugins.php or add filters to
bp_template_title and bp_template_content
------------------------------------+-----------------------
Reporter: modemlooper | Owner:
Type: defect (bug) | Status: reopened
Priority: normal | Milestone: 1.7
Component: Theme | Version: 1.7
Severity: normal | Resolution:
Keywords: has-patch dev-feedback |
------------------------------------+-----------------------
Changes (by r-a-y):
* keywords: reporter-feedback => has-patch dev-feedback
* type: enhancement => defect (bug)
* version: => 1.7
* component: Core => Theme
* milestone: Future Release => 1.7
Comment:
Okay, I see a problem with plugins.php in bp-default. And I believe I see
what modemlooper was referring to.
In bp-default, specifically `/members/single/home.php`, there is a call to
plugins.php, however the actual `/members/single/plugins.php` in bp-
default is a full template (with get_header() / get_footer() calls) rather
than a template part.
However, bp-legacy uses `plugins.php` as a template part. So there is a
discrepency between bp-default and bp-legacy. The problem is going to be
addressing this so both bp-default and bp-legacy reference the same thing.
A solution I see is to leave bp-default's plugins.php alone for backpat,
but introduce a new file called `generic.php`, which acts as a template
part for plugins. To be compatible with bp-legacy, I have renamed
`plugins.php` to `generic.php`. `01.patch` illustrates what I mean.
If the other devs agree, we'll need to do the same thing with the groups
component.
I know this is a late change in the game, but I think it's necessary.
--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/4855#comment:16>
BuddyPress <http://buddypress.org/>
BuddyPress
More information about the buddypress-trac
mailing list