B. At the bottom of the same 16 files, replace:
`
`
with the following (except for registration/register.php):
`
<?php if (get_option_tree('blog_layout_sidebar', '')) {} else {echo '
‘;}?>
`
with the following for registration/register.php:
`
<?php if (get_option_tree('blog_layout_sidebar', '')) {} else {echo '
‘;}?>
jQuery(document).ready( function() {
if ( jQuery(‘div#blog-details’).length && !jQuery(‘div#blog-details’).hasClass(‘show’) )
jQuery(‘div#blog-details’).toggle();
jQuery( ‘input#signup_with_blog’ ).click( function() {
jQuery(‘div#blog-details’).fadeOut().toggle();
});
});
`
Save files.
C. Upload the 6 BP folders containing the 16 files you’ve just revised to your server wp-content/themes/Paediatric/
D. Copy the style modifications made in BP Twenty Ten at https://codex.buddypress.org/theme-development/theme-dev-bp-template-pack-walkthrough-twenty-ten-bp-1-5/3/ and paste to your theme’s stylesheet. Adjust to taste.
Final note: not sure whether the options re sidebar locations will work in BP template files with your theme. Some themes have options that work, some themes not at all. Make the top and bottom revisions with /members/index.php to start and see how that works out first.
@benzine You need to change 16 template files within the 6 BP folders transferred to your Paediatric theme folder in server during the compatibility process.
If you’ve previously changed any of the BP template files in your Paediatric theme folder in server, replace all of them for a clean slate by deleting the 6 BP folders – /activity, /blogs, /forums, /groups, /members, and /registration – then re-run Appearance > BP Compatibility.
Download the 6 clean BP folders to your computer hard drive.
A. At the top of each of those 16 template files I linked to above, replace
`
`
with the following:
`
<?php if (get_option_tree('blog_layout_sidebar', '')) { echo '
‘; } else {echo ‘
‘;} ?>
<div id="post-” >
`
Then, in each of 16 files, delete the BP Templates’ Page titles where found (usually found in index.php files within BP Template folders) since the BP titles are generated automatically during the BP Installation Wizard and you don’t want duplicate titles in one page. Be careful with the activity/index.php file.
Save files.
@michaelgossling
– After you activated BuddyPress, did you go through the Installation Wizard? https://codex.buddypress.org/getting-started/setting-up-a-new-installation/installation-wizard/
– After you activated the BP Template Pack plugin, did you go through the process via dashboard menu > Appearance > BP Compatibility and finish Step 3 (match HTML structure of theme with BP templates)?
Hi, thanks for your kind reply. I appreciate, but that completely removes the adminbar (including the Buddybar). I want to remove the WORDPRESS admin bar alone from non admins, but NEVER the Buddypress adminbar, which I want to have visible at all times…..
Possible?
Thanks!
9087877Inactive
I can understand how some people could get confused to what the best solution is because you have bp-album, bp-media, bp-gallery, bp-media component etc. and it would be awesome if the most fully featured of the media plugins was either integrated or somehow auto-suggested in the BuddyPress install. Anyway, that is just my opinion, and I think it would save a little confusion for those that are new to BuddyPress.
== the duplicate wp_head is not really giving me serious issues (apart from that redirect problem at the moment), however it’s wrong to have repeated js and css in a page ==
@substrato Re duplicate wp_head, how did you create header-buddypress.php? I do it by opening up header.php file and Save As > header-buddypress.php then at the bottom of that new file, add the necessary HTML tags which are not available in the BP templates. A possibility could be that you replicated wp_head in your our header-buddypress.php which I assumed you checked already?
@rodtrent I placed it in the bp-custom.php and in bp-loader.php Line 482 at the end of the function `setup_actions()`
@helllllpmeplease I can see the activity comments in the two page links you posted in IE8, then when I removed styles on the pages in FF15 the unstyled posts are there. This means that something’s gone awry with the BP compatibility process.
Download permalink.php from your server wp-content/themes/clearline/members/single/activity/permalink.php to your computer hard drive. Open it up with a text editor like Notepad and delete everthing within. Copy the following and paste it to your permalink.php file
`
`
Save permalink.php and upload to wp-content/themes/clearline/members/single/activity/ folder. Clear cache and check it out.
Great idea @r-a-y , will try it tonight , I would like to use it for custom post type answers
I simply went to the buddypress/bp-loader.php file and pasted the code below at the end of the file…
Try adding this code snippet to your wp-content/plugins/bp-custom.php:
remove_action( ‘bp_template_redirect’, ‘bp_redirect_canonical’, 2 );
This will remove the canonical redirect hook that might be causing you some issues.
I’ve developed my own theme, I just copied the files provided into my own theme, then added a simple div tag in header-buddypress and closed in footer-buddypress to encapsulate it inside my existing css blocks
if I don’t create these two files buddypress will look funny
sorry for the confusione about my sentence above, I meant I’m not using a third party theme, I’m developing my own and embedding buddypress into it with BP Template Pack
other than the issues mentioned above, my buddpress and wordpress installation are working fine; the duplicate wp_head is not really giving me serious issues (apart from that redirect problem at the moment), however it’s wrong to have repeated js and css in a page
Good luck. I use BP Gallery myself 
@aces I placed this line in my bp-custom.php, but that did not help….
I don’t know how to thank you !
Have A REAL nice time ! 
No, really. I *know* BP doesn’t touch or do anything with XMLRPC. If it’s causing a problem, it’s a symptom of something else. e.g. things like load order, or something like that.
Ok, here we go again 
loop.php -> http://pastebin.com/hY4QRvdS
loop-page.php -> http://pastebin.com/3e3KVhuh
loop-single -> http://pastebin.com/awtQMxpZ
I greatly appreciate your help man, and hope this can be solved asap.
Peace xxx
Happy Thursday @mercime! Here are links to the following issues I mentioned in the first post, and I hope they help!
1) http://shenow.org/featured-women/member-directory/members-2/neyloeza23/ – When you put the link in your browser, you’ll see conversations by this member and just under each one is a “View” link. The “view” button is working in chrome, but not in firefox or IE.
2) When a user is mentioned on the activity page, they receive an email with a link to take them directly to the conversation…for example: http://shenow.org/activity/p/2270/ (you do not need to be logged in) The link works in Google Chrome, but it does not work IE or Firefox.
I’m using Firefox 15.0 and IE 9.0 – I know it’s not just me as I’ve had complaints from users about the links not working for them either.
I look forward to seeing what you think/find!! Thanks @mercime
You would *think* BP doesn’t touch XMLRPC at all, but here’s the scenario…
Pre BP 1.6x – works fine. Windows Live Writer connects and works. JetPack can connect.
Post BP 1.6x – With BP activated, Windows Live Writer cannot post to WordPress. You have to disable BP before JetPack will connect correctly – gives error about XMLRPC. So, something that BP is doing when enabled, locks XMLRPC.
I’ve reported this to the JetPack folks and they are checking into it.
Thank you, I suspected that was the case.
BP doesn’t touch XMLRPC *at all*. It’s probably coincidence and will hopefully resolve itself whenever the route issue is fixed.
I have no experience with IIS so unable to help further; at least we proved it’s not the canonical redirects causing trouble.
Gave it a shot, but had no affect. Same issue. If I could get the profiles issue resolved (too many redirects), I can circle back to the others. It’s just strange that Buddypress “locks” the XMLRPC file.
@benzine your page.php has `get_template_part( ‘loop’, ‘page’ )` so do post the code for loop-page.php in pastebin.com as well