BuddyPress.org

It’s not really a core hack. Functions.php is meant to be edited.

The BP Home theme is just a mask over WPMU’s eyes. It uses functions.php to play some tricks on WPMU to allow it to hijack some urls. All that you’re doing is hardcoding it yourself.

Lo.

> Why is it when I add a page to my WordPress site, it doesn’t show up in my BuddyPress navigation?

Because that’s just the way the default home theme is written. The items listed on that menu aren’t ‘Pages’ in the WordPress sense, anyway, so it makes little sense for the default, out-the-box BuddyPress theme to do that.

The bit of code you’d need to change (or to add in your custom/duplicate theme) is in header.php. Where you see:

<ul id="nav">

Add this underneath:

<?php wp_list_pages('title_li=<h2>Pages</h2>' ); ?>

Documentation for that function is at https://codex.wordpress.org/wp_list_pages

Inside your functions.php for your home theme, comment out:

function bp_show_home_blog() {

......

}

John,

Just checked out delsolownersclub.com. Really like the way all parts of the website are well integrated (including the forum)

The bp home theme is entirely optional. You can use your preferred wp theme for all the usual things and integrate whatever selected features what you want into the theme. Or none at all. The member theme is still available through the top admin bar.

See this in the codex: https://codex.buddypress.org/getting-started/using-the-buddypress-themes/

Hardcoding them into the sidebar is the only way to have them not be editable for a user.

Andrea_r is also correct from page 1 about the user blog edits. I’ve had that exact setup over at http://delsolownersclub.com working for about 3 months now smoothly and seamlessly (doing some cross posting in two topics now.)

Like Andy said, the “Home” theme is really intended only for the “Home Blog” or the main blog that your website is responsible for. It’s intent is similar to a “portal” page for those of you familiar with phpNuke, vBulletin, etc…

Think of wordpress.com…

There’s a page there that shows all sorts of SITE WIDE content. Then you can drill down into users blogs, and see their specific blogs and themes. Exact same idea with the home theme.

Using the Home theme as a user blog will result in errors, because the “Members” and “Groups” and “Blogs” links don\’t exist under sub domains/directories.

For a “seamless” type of interaction, you will want to make a duplicate of your “Home” theme, call it “User”, edit the style.css to give it a new name, delete home.php, and edit the header.php file to use$bp->root_domain in place of get_option('home')

This is what I did for http://delsolownersclub.com. You’ll notice that the user blogs look just like the home blog.

It used to be that wp didn’t consider the member theme a theme at all. It still doesn’t. Andy is temporarily tricking wp by trapping a couple of filter calls that wp uses to find the current theme. Looks like when we are in the member theme wp temporarily thinks it’s the current theme.

This makes sense, because like you said above, the Member Themes aren’t real WordPress themes; BuddyPress just muscles itself in and takes over the place. And as long as the member theme functions.php registers a sidebar with the same name, WP doesn’t know the difference and loads it up.

It’s posts like this, Burt, that lead me to believe that there’s a whole lot of progress that will be made in modifying the Member Theme area.

Good post, A+ for the day.

Once again the major restriction I’ve found is that the functions.php files in both the member theme and the home theme *must* register the same sidebars. They have to match. The member theme can not independently register a sidebar that doesn’t exist for blog id 1.

I can live with that.

That\’s how I got the member theme to display a sidebar using the plugin-template.php and plugin-sidebar.php templates. You\’ll have to modify the directory templates to display a sidebar if you want them to show up there. All you have to do is include the sidebar div like:

<div id="sidebar">

<?php if ( !function_exists('dynamic_sidebar') || !dynamic_sidebar('member-sidebar') ) : ?>

<?php endif; ?>

</div>

I stuck that each directory’s index.php template and modified the css to format things properly. Giving the new sidebar some room.

The last time i fooled around with the member theme at the sidebar/widget level I couldn’t use dynamic sidebars. It was just flatly impossible. Seems things have changed. I’ve gotten them running in the member theme but have only been able to select sidebars that are defined in whatever theme I have defined for the wp blog id 1 theme.

Like I say it’s been quite awhile since I looked at this problem and to my surprise it actually works now. Sort of, with restrictions, kinda. Perhaps I’m just doing it the wrong way. I’ll tell you how I got it done.

The problem really is that the member theme isn’t a real registered theme. You only get one theme per blog with wp. That one is the one activated for that particular blog. I currently have the bp home theme registered for blog id 1. It registers 3 sidebars and those are the ones that are available for the theme.

The bp member theme doesn’t register any sidebars by default and doesn’t include the default sidebar template file either. I suggested above that you use the sidebar template from the home theme. That alone was not enough to get widgets into the member theme. I stuck the normal code for using dynamic sidebars into the sidebar template like this:

<?php if ( !function_exists('dynamic_sidebar') || !dynamic_sidebar() ) : ?>

<?php endif; ?>

That got me exactly nothing. So I included sidebar registration code in the member theme’s functions.php file where it normally gets put.

register_sidebars( 1,

array(

'name' => 'member-sidebar',

'before_widget' => '<div id="%1$s" class="widget %2$s">',

'after_widget' => '</div>',

'before_title' => '<h2 class="widgettitle">',

'after_title' => '</h2>'

)

);

I named my new sidebar ‘member-sidebar’ thinking that it would show up in the back end of wp where I could then register some widgets for my ‘member-sidebar’. Nope. The ‘member-sidebar’ doesn’t show up.

I did get the first sidebar to display in the member theme though. Whatever was defined in the wp theme as the first registered sidebar, showed in the member theme. Well this is progress ‘eh? Something is showing in the member theme. I had to mod the member theme css to have it appear though. The #sidebar div isn’t in the base.css for the member theme. I modified the #content div in base.css and included the new #sidebar div.

Still with me? Now I have *a* sidebar with widgets in the member theme. Well I don’t want just any widgets, I want to specify what specific widgets get displayed right? Anyway I finally figured out that I have to register *all* the same sidebars that the wp theme on blog id 1 register. I copied all the function.php sidebar registration calls from the home theme’s function.php and stuffed them into the member theme’s function.php.

Works like a charm. Now in my member theme template file plugin-sidebar.php I can specify which sidebar I want to display.

<?php if ( !function_exists('dynamic_sidebar') || !dynamic_sidebar('blog-sidebar') ) : ?>

That above just happens to be the one I chose to test that I could have any sidebar I wanted in that template. Works. Well, I didn’t want one of those sidebars at all. I wanted a separate sidebar for my member theme. ‘member-sidebar’. That would not show up until I included the registration function in both the home theme and the member theme. Then I get to change the code above to be ‘member-sidebar’.

Like I said I may be doing this all wrong and hope that someone comes up with a better solution but this is the one that works for me.

1) Add another register sidebar call to the wp theme running on blog id 1. Like this in your blog id 1 functions.php file:

register_sidebars( 1,

array(

'name' => 'member-sidebar',

'before_widget' => '<div id="%1$s" class="widget %2$s">',

'after_widget' => '</div>',

'before_title' => '<h2 class="widgettitle">',

'after_title' => '</h2>'

)

);

I stuck that under the other 3 calls in the default home theme.

2) Copy *all* the register_sidebars() calls from the home theme functions.php file to the member theme’s functions.php file. They should look the same now when it comes to sidebar registration calls.

3) Copy the sidebar template file that is distributed with the home theme plugin-sidebar.php to the member theme dir.

4) Modify the plugin-template.php file in the member theme to load the new sidebar template also.

<?php get_header() ?>



<div class="content-header">

<?php do_action('bp_template_content_header') ?>

</div>



<div id="content">

<h2><?php do_action('bp_template_title') ?></h2>



<?php do_action('bp_template_content') ?>

</div>

<?php bp_get_plugin_sidebar(); ?>

<?php get_footer() ?>

That’s my plugin-template.php file that lives in my member theme.

5) Modify the plugin-sidebar.php template in the member theme to look like this:

<div id="sidebar">

<?php do_action('bp_template_sidebar') ?>

<?php if ( !function_exists('dynamic_sidebar') || !dynamic_sidebar('member-sidebar') ) : ?>

<?php endif; ?>

</div>

6) Modify the member theme css to include the new #sidebar div that didn’t exist before. I just did it this way for the content and sidebar divs:

#main #sidebar{

margin-left:70%;

margin-right:20px;

}

#main #content {

float: left;

width: 65%;

position: relative;

padding: 2em 3em;

}

Use whatever is appropriate for your member theme.

7) Fire up the back end of wp and add widgets to the ‘member-sidebar’. Enjoy your new member theme sidebar.

i am using facebuddy done by sgrunt. also not working even with default theme.

“Member blogs come up, but each new member would have to configure their own widgets.

I’d like members to be able to join and have everything set up for them. “

this comes up under basic WPMU blog defaults, and is covered extensively over in that forum. there’s even 2 plugins available to set blog defaults.

with widgets it’s a little different – if you don’t want them to change anything, don’t use widgets. hardcode it in the theme sidebar.

After disabling bphome and just running on the classic wordpress theme whenever I visit any of the pages that involve BP scripts I get the error.

A classic WordPress theme will not work with BuddyPress. There is BP-specific code within BP themes and BP theme folders. The question is, what happens when you use the standard BP themes that come with BuddyPress?

Also, after switching to the standard BP themes, and if you’re still having issues, then you should set PHP to run on version 5 instead of 4 and see what happens.

I’ve been having the same problems. All the theme files were placed in the right spots and now a few of the pages on the front end work, but most of the user specific stuff is still popping 404s. I have a post in the how-to section that died about about this topic. Looks like we’re S.O.L. for a bit until someone has a eureka moment.

The 1.0 member theme plugin-template.php doesn’t include the sidebar. You’ll have to copy the plugin-sidebar.php template over to the member theme dir. Also the plugin-template.php file doesn’t include the call to launch it. If you look at the home theme’s plugin-template.php file you’ll see the difference. It has a diff set of divs and a call to bp_template_sidebar() which you’ll have to include in the member theme’s plugin-template.php.

You do know that this doesn’t really setup a normal wp sidebar were you can install widgets from the back end of wp right? All the sidebar does is trigger an action that you have to trap in your code.

Warning: bp_show_register_page(BP_PLUGIN_DIR/bp-core/bp-core-signup.php) [function.bp-show-register-page]: failed to open stream: No such file or directory in /home/www/missionaries.net/wp-content/themes/buddypress-home/functions.php on line 70

Did you deactivate the bp plugin? It doesn’t seem to be running. If it’s not available for selection then check the /wp-content/plugin dir for it’s existence. If it doesn’t exist reinstall it.

Finding out why it got deactivated or it doesn’t exist anymore would be the next step.

Okay, I’ve reread this thread for the second time. You state that:

The problem must be with the data; since a fresh install works perfectly and after the data gets imported, I get the nasty 404 bug.

Andy’s answer is:

This is normal with WPMU, you are not going to be able to transfer over blog tables as there are all sorts of URL settings in the DB.

I have a few questions based on this interchange:

1. Which version of MySQL are you (is your host) running?
2. Have you tried repairing the DB tables before reimport?
3. Are you moving your data between different domains?

Since WPMU 2.7.1 + BuddyPress 1.0 + standard themes work fine with a new, empty MySQL DB, the issue is, as you state, with the data. Either you have data corruption, indices that need reindexing, or hardcoded links within the tables that are causing the 404s.

If the domain mapping is not identical to the hardcoded links in your WPMU tables, you will have issues.

So, here’s what I’d suggest:

1. Backup your data again
2. Then, repair/reindex
3. Then, if your domain mapping is not identical, follow these instructions keeping in mind that these articles are for WP and not WPMU. You’ll have to adjust accordingly:

   • https://codex.wordpress.org/Changing_The_Site_URL
   • https://codex.wordpress.org/Moving_WordPress

Ilya,

I’m working on a project where i must integrate WPMU, buddypress and bbpress all together.

http://terafriu.com/forum/ is the forum page. I have modified the kakumei theme that came with bbpress. Changing the header and footer will go a long way. But it ultimatly depends on what you are trying to acheive. For the time being you’ll either have to create/modify your own.

Keep in mind that Buddypress is a fairly new application and we should be gratefull to get such an application for free! When the important stuff like bug fixes etc are resolved we will see tons of themes, just like WordPress.

here’s something i have lying around. i’m not sure where i got it. not very good at records:

<?php

function add_about_to_main_menu() {

$class = (bp_is_page(‘about’)) ? ‘ class=”selected” ‘ : ”;

echo ‘<li ‘ . $class. ‘>‘ . __( ‘About’, ‘buddypress’ ) .’‘;

}

add_action(‘bp_nav_items’,’add_about_to_main_menu’);

?>

end here.

create this as something like aboutmenu.php then edit the link (href part). this way you wont have to muck around the theme files.

hope that helped!

You’ll have to edit the css-file in your member-theme.

In the css/base.css file you’ll find something like this:

Just copy that and change the “a#user-settings” to whatever fits your component, like “a#the-navigation-slug”. Don’t forget to put your image in the according folder and changing the name in the code to that name.