This is a problem with your theme.
BP theme compatibility is designed to automagically use standards WP templates if certain custom ones aren’t found, assuming you haven’t created any custom files in your theme BP is looking for these files in this order:
page.php
single.php
index.php
If you theme does not have these or use one in a standard manner then you may well get a screwy layout, but it’s going to be very hard to tell you what is going on with a third party theme like this.
Looking at BP pages I can see straight away something not quite right as there is a distinct lack of WP/BP body classes that I would expect to see.
You’re going to need to look those standard files above, determine which is being used by BP components in theme compat mode then try and work out what your framework is using to generate your general page.php page views i.e what file is used when you create a WP ‘page’.
Here is single.php…
Here is Page.php
<?php
/**
* @package WordPress
* @subpackage Constructor
*/
wp_enqueue_script( 'comment-reply' );
// load header.php
get_header();
// load one of layout pages (layouts/*.php) based on settings
get_constructor_layout('page');
// load footer.php
get_footer();
Here is index.php…
Where should I look next and what should I change?
Thanks for your help.
Cheers
Roy
hmm… I pasted all three, but only one showed up.. 2nd try… here is single.php…
hmm… dont know where they go to…
index.php…
/**
* @package WordPress
* @subpackage constructor
*/
// Stupid Parser This is Theme support the Gravatar Service
// get_avatar();
// load header.php
get_header();
// load one of layout pages (layouts/*.php) based on settings
get_constructor_layout(‘index’);
// load footer.php
get_footer();
single.php
/**
* @package WordPress
* @subpackage Constructor
*/
// requeried comments
wp_enqueue_script( ‘comment-reply’ );
// load header.php
get_header();
// load one of layout pages (layouts/*.php) based on settings
get_constructor_layout(‘single’);
// load footer.php
get_footer();
Just a note:
open and close php are removed as I think that is causing the entire file to not show up…
and what is in this file:
// load one of layout pages (layouts/*.php) based on settings
get_constructor_layout(‘page’);
This is going to be a problem with these frameworks that break with the normal WP methods for their own approach to templating and where users are going to have to figure out how to deal with this.
You could try creating a file named buddypress.php in your theme root and in that file copy the contents of what ever is in layouts/page.php but that file may also not be standard.
Oh and you ought really to ask this question of the theme authors, as they are the ones that have diverged from the norm so are best placed to understand or know how they have and how that has been done and suggest an approach you can take. They just need to know that BP attempts to use the standard WP templates and the content loop replaced with BP content.
Failing all the above you may need to fall back on the older method of overloading BP templates into your child and ensuring the markup matches to the themes markup.
You may like to look through the codex to see if the constructor theme has been template packed by Mercime.
Having looked further at this theme framework on a local test install and it appears to work pretty well in it’s default out of the box implementation with BP 1.7 so I’m afraid whatever custom settings / layout configurations you have set in the frameworks backend are causing issues.
Hugo.
Thanks very much for that follow-up information.
I don’t know what I should do about that. Should I just delete everything and start again?
Hugo. I deleted the entire Constructor Theme folder using FTP and then reinstalled the constructor theme. Presto, bingo! It worked flawlessly with 1.7! Woohoo! You have no idea how excited I am about that! So, a huge thanks for your help!
Glad to hear it. It may be the case however that as you start to customize those layouts that things go awry as the themes proprietary approaches to building pages from the backend kicks in but overall it didn’t look too bad on simple activation.
Yes, I think that is possible. My solution is to try to get back to my original layout step by step and check after every change whether it causes the problem.
That’s the way to approach it then you know exactly at what point and at what function things went awry at, makes it easier to focus on the reason.
