Remember also, that the navigation in header.php has NOTHING to do with WordPress pages. They are hard coded to the BuddyPress predetermined hi-jacked URLs.
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/
bp has to be installed in a folder called /wp-content/plugins/buddypress. Try uploading the plugin again. Activate sitewide.
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. 
Since this is a BuddyPress forum, I’ll assume you’re talking about the Buddypress widget “Recent Blog Posts” and not the WordPress widget “Recent Posts”
You need to look in bp-blogs-widgets.php for the code. But, do not change the code within that file. It is a core BuddyPress file and any changes you make will be lost the next time you upgrade. Instead, make a copy of that file and create your own custom widget.
Derosion-
Although the WordPress widget API clearly advises developers not to use the widget functions starting with wp_, there is an issue with localization of Widgets in BuddyPress if the register_sidebar_widget() is used.
If you’re not planning on distributing your custom components or widgets, then you can code them with the register_sidebar_widget() function call instead of wp_register_sidebar_widget(). However, if you plan to make your custom component or widget available to the community, you should use wp_register_sidebar_widget() at this time.
See Changeset 1244 for more information.
Mariahneu-
First of all, we need some additional information:
- Which version of WordPress Mu are you running?
- From where (provide link) did you download WPMU?
- Which version of BuddyPress are you running?
- Did you open any of the BuddyPress files?
- Did you alter any of the BuddyPress files?
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.
Not yet. To do that we’ll need to save also in buddypress tables id of assigned site, or – probably easier to accomplish – create different instances of buddypress with all tables for each site.
Till now i found out that manipulating with define( ‘BP_ROOT_BLOG’, $blog_id ); (line 16,bp-core) i can make social part avaiable from each site. the problem is that avatars on other sites disappeared and – of course – i’m afraid about google and duplicated content issue.
My goal is to have on ‘global’ buddypress instance and ‘local’ buddypress instances for each site. The only thing i’m afraid about is number of tables and queries to load each site on such a configuration…
Were you also able to separate out the friends and groups so that the groups and friends associated with Site A were not seen by people on Site B?
Ops – part to site_id should be as follows:
function my_bp_adminbar_authors_menu() {
global $current_blog,$wpdb;
$blog_url = get_blog_option($current_blog->blog_id, 'siteurl' );
$blog_url_pieces = explode("/", $blog_url);
$blog_url = $blog_url_pieces[2];
$site_id = $wpdb->get_var( "SELECT COUNT(*) FROM wp_site WHERE domain='".$blog_url."'");
I’ve redownloaded everything back to the original server, and even made sure to upload (specifically) the bp-themes folder from here. 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.
You do not have any BuddyPress themes installed.
Please move “/wp-content/plugins/buddypress/bp-themes/” to “/wp-content/bp-themes/” and refresh this page. You can download more themes here.
The files are in the right place and when I go to BuddyPress settings as a site administrator both the bpmember and skeleton member themes are available. I’ve tried the click it method I’ve seen in other posts but its not working. Do you have another tactic at fixing that situation? I think that is whats causing the majority of these 404’s.
Updated bp_adminbar_authors_menu to hide authors on additional main sites
//HOOKS FOR TOP MENU - AUTHORS
remove_action( 'bp_adminbar_menus', 'bp_adminbar_authors_menu', 12 );
add_action( 'bp_adminbar_menus', 'my_bp_adminbar_authors_menu', 12 );
// **** "Blog Authors" Menu (visible when not logged in) ********
function my_bp_adminbar_authors_menu() {
global $current_blog,$wpdb;
$site_id = $wpdb->get_var( "SELECT COUNT(*) FROM wp_site WHERE id=".$current_blog->blog_id);
//$numrows = $wpdb->num_rows($site_id);
if ( $site_id!
'1' ) {
$authors = get_users_of_blog();
if ( is_array( $authors ) ) {
/* This is a blog, render a menu with links to all authors */
echo '<li id="bp-adminbar-authors-menu" class="'.$site_id.'"><a href="/">';
_e('Blog Authors', 'buddypress');
echo '</a>';
echo '<ul class="author-list">';
foreach( $authors as $author ) {
$author = new BP_Core_User( $author->user_id );
echo '<li>';
echo '<a href="' . $author->user_url . '">';
echo $author->avatar_mini;
echo ' ' . $author->fullname;
echo '<span class="activity">' . $author->last_active . '</span>';
echo '</a>';
echo '<div class="admin-bar-clear"></div>';
echo '</li>';
}
echo '</ul>';
echo '</li>';
}
}
}
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.
great addition Burt, didn’t even think about that. it works great!
custom.css doesn’t work in this case people? custom.css should override base.css without a direct edit of base.css. I’m just getting to this at the end of the discussion.
Jotem = Genius!
That worked, thanks! I hate core hacks, but looks like it wasn’t going to work any other way.
Evvscuba-
We have no idea what setup you’re running? Which version of WPMU, of BuddyPress? How did you install them? Did you upgrade WPMU? If so, from which version and how?
Also, please first visit and read the link I provided in the second post. If the suggestions there do not solve your problem, then answer my additional questions in the fourth post.
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:
- Which version of MySQL are you (is your host) running?
- Have you tried repairing the DB tables before reimport?
- 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:
- Backup your data again
- Then, repair/reindex
- 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:
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:
li a#user-settings, li a#my-settings {
background: url(../images/settings_bullet.gif) 88% 52% no-repeat;
}
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.
This is a wpmu/bbpress integration issue not a bp issue as far as I can tell. Since this is not a bp support issue, marking the thread as such.
