Template hierarchy for /groups/single/plugins.php and /members/single/plugins.php

[henrywright]

​http://codex.buddypress.org/developer/theme-development/template-hierarchy/

Just some feedback with reference to the advanced template hierarchy going into BP 1.8

1. It doesn't mention the forums main page in the template hierarchy in the Codex. Will there be a template hierarchy for this?

2. I noticed that the templates for the registration page (index-register.php) and activation page (index-activate.php) are filed under members (buddypress/members/*.php). If the same folder structure as bp-default is to be used, shouldn't these templates be filed under registration (buddypress/registration/*.php)?

3. Some plugins use the plugins.php file to output information, will this be in the hierarchy e.g something like buddypress/plugins/plugin-{plugin-name}.php

Hope this helps development/testing.

[boonebgorges]

Thanks for the feedback, henrywright.

Will there be a template hierarchy for this?

Not for 1.8. We're not providing any additional enhancements for bbPress 1.x. As for bbPress 2.x (the plugin), that'd fall under your #3, but it's not slated for this release.

noticed that the templates for the registration page (index-register.php) and activation page (index-activate.php) are filed under members (buddypress/members/*.php)

These were moved to members in 1.7 bp-legacy. I think the idea was to get rid of an unnecessary template directory. bp-default still has the old format, for backward compatibility reasons only.

Some plugins use the plugins.php file to output information, will this be in the hierarchy e.g something like buddypress/plugins/plugin-{plugin-name}.php

This is a great suggestion. It's too late to do this for 1.8 (and also there are probably going to be some technical hurdles to making it work, because BP doesn't have a reliable way of telling which plugin is calling a given template), but I'm going to move this ticket into the 1.9 milestone and rename it to reflect the suggestion. We can talk about it more in the next cycle.

[boonebgorges]

Bumping this due to lack of patch. It might end up being fairly straightforward, so I'm moving to 2.1 for further review.

[DJPaul]

We're closing this ticket because it has not received any contribution or comments for at least two years. We have decided that it is better to close tickets that are good ideas, which have not gotten (or are unlikely to get) contributions, rather than keep things open indefinitely. This will help us share a more realistic roadmap for BuddyPress with you.

Everyone very much appreciates the time and effort that you spent sharing your idea with us. On behalf of the entire BuddyPress team, thank you.

If you feel strongly that this enhancement should still be added to BuddyPress, and you are able to contribute effort towards it, we encourage you to re-open the ticket, or start a discussion about it in our Slack channel. Please consider that time has proven that good ideas without contributions do not get built.

For more information, see ​https://bpdevel.wordpress.com/2018/01/21/our-awaiting-contributions-milestone-contains/
or find us on Slack, in the #buddypress channel: ​https://make.wordpress.org/chat/