not sure why this is of concern, and I am not a bp expert.. however I would make a full backup of all files (via ftp or filemananager with a zip or something) – then export a copy of your database (through phpmyadmin for example (be sure to check off the box for “add drop table (or whatever it is called) –
then go in and delete the old theme that is still showing up in appearance themes…
and if everything is still working.. then your problem is solved (?)
Thanks for your answer.
I don’t care whether or not the template shows up there 🙂 but I am interpreting this as a sign that it is still in use somehow, which should not be the case.
Update:
I copied my theme/buddypress directory into the twentyfourteen directory and now my files are being included. So the problem is with my theme. What could cause the template hierarchy to be ignored in a custom theme? I’ll try getting rid of as much as possible to see if I can get it work.
I read that the BP default theme has been retired and should not show up under Appearance > Themes unless it’s still in use.
That’s not quite true. If you can remember where you read it, please let me know, and I’ll see about correcting the information.
If you had a BuddyPress site prior to version 2.0, then we will always make BP-Default available in the themes list. If you were to install BuddyPress today on a new site that did not have BuddyPress installed before, then it would not show up. I hope that makes sense.
(I’m not sure if we started this behaviour in version 1.9 or 2.0, but it was around then).
From reading that documentation, it looks like the files are named correctly. I’m not sure.
Maybe @hnla or @henrywright
I read it here and here, but maybe it will always show up as you said because we updated from an earlier version.
The files are named correctly, as with the twentyfourteen theme the files are being included.
My next step will be to build a theme from scratch and see if I can get it to include the files.
@chlab @djpaul
The template hiearchy advanced template names are correct and will overload any theme compat files as long as they are located in correct directories, and by the sound of things you have established this on a stock WP theme ( always remember that with template names such as index-create.php we are saying take full control of the template rendering bypassing BP’s content injection so the template needs to be a full WP template i.e one complete with header call and footer call and all necesary content inbetween)
Things that can force deactivate theme compatibility are:
* Theme compat is disabled when a theme meets one of the following criteria:
* 1) It declares BP support with add_theme_support( 'buddypress' )
* 2) It is bp-default, or a child theme of bp-default
* 3) A legacy template is found at members/members-loop.php. This is a
* fallback check for themes that were derived from bp-default, and have
* not been updated for BP 1.7+; we make the assumption that any theme in
* this category will have the members-loop.php template, and so use its
* presence as an indicator that theme compatibility is not required
Pay special attention to the possibility of members-loop.php existing from previous implementation of this custom theme in the themes root i.e members/members-loop.php
And check through any functions files for inclusion of :
add_theme_support( 'buddypress' )
Both or either of these will deactivate theme compatibility and likely result in navigating to /groups/ simply displaying a plain stock WP page.php view.
Thanks Hugo, that helps. It was the style.css. It hat a Template: bp-default in it. I didn’t notice it at first because our theme is named similarly and my mind read it as the title of our theme. If I remove it, my templates are included.
Now I have to find out how to upgrade the theme so it no longer relies on the bp-default theme.
