As of WPMU 2.8.1 this will work, but with 2.7.1 if you changed an email address, it didn’t get changed in wp_signups, so even if you changed the email address, you still could not reuse the original one you used to sign up. Be careful right now using 2.8.1 as there are several ways that it’s not playing friendly with BuddyPress.
A user-switching plugin is probably the easiest and safest bet, in my opinion.
WPMU 2.8.1 and BuddyPress 1.0.3 have a few issues at the moment. Would be best to use WPMU 2.7.1, or wait until 1.0.4 is released.
If you need to use 2.8.1, then as much as I usually never like to say so, you might be better off using the latest trunk version. I’ve been running it for a few days now fully integrated with no issues that are obvious or apparent.
My recommending to use the trunk always comes with the assortment of warnings that it might be broken in some places or unfinished in others, so be careful of that too. Trunk versions aren’t really meant for public use, but it seems everyone is becoming more comfortable doing it recently.
Also, for group forums to work, your hosting package must allow for XMLRPC, as well as having them both turned on in each *press platform. More than likely something is out of alignment somewhere and even though you swear it’s not, it really is. 
To begin with, I would start by following these tutorials:
https://buddypress.org/forums/topic/bp-103-and-bbpress-which-version-plugins-cookies
http://theeasybutton.com/blog/2009/07/17/integrating-buddypress-wordpress-mu-and-bbpress/
BTW, regarding user mapping, the only setting I changed was WP Admin one, mapped to bbPress Key Master. The other four settings remain untouched.
I am still on 2.71 and 1.01 so can’t help directly with version issues but have you definitely put the correct details in the Forums Setup within the BuddyPress dashboard area?
New development. The Buddypress.org/blog/page/2/ URL no longer directs you to an error page, but instead gives you the same list of posts as on the first page.
Also, a solution was posted in the bug tracker: https://trac.buddypress.org/attachment/ticket/854/page_2.2.patch but it did not work for me. I’m not sure if its my own stupidity in not realizing where to put it (bp-core/bp-core-catchuri.php?) but it didn’t change anything on my site. I’m still getting the “Sorry, No posts match your criteria”.
In short: HELP!
Just launched a new BuddyPress based site for a client who was running a normal WordPress based site before hand:
http://sharemyplaylists.com/
The site has been set up as a music community site for people who use the music service Spotify and want to do more than ‘just’ submitting their playlists.
Lots of issues and things we have learnt about BuddyPress, WordPress MU etc during the delelopment and hopefully now the site is launched we might have more time to get involved answering questions on these forums rather than asking them 
3572699Inactive
Wait wait, I got it – sorry. I reinstalled buddypress and that did the trick. Thanks!
Note that the default home theme for buddypress already links to the member profile. If you are using another theme – awesome!
Hi cozzie,
As Andy has stated above, the Dashboard is just a few BP loops on one page (with exception to the bbPress favorites section!).
Read up on BP loops here:
https://codex.buddypress.org/developer-docs/custom-buddypress-loops/
I actually started building my own dashboard-like page for members (kind of mirroring BP’s) and I really dig the BP loops, especially the documentation – that really helped.
That worked! Thanks again
There have been several threads about this, including some useful code, but also lots of loose ends and confusion:
Securing components from non logged in users
Make access members/groups sections members-only
Plugin to show components to registered Users only
Apparently a “full-featured privacy (authorization) component for BuddyPress” is in the works for a future release.
I dont’t know which features I’ll eventually add…
As said above, I’m not a professional coder and it is a challenge for me to finish this as it is
But it’s true, it’s a good idea. I’ll see later.
No widgets planned for the moment (only maybe things like last/random classifieds) and plan to make it different from the others as it is completely build on BuddyPress, with its code & features (notifications, member screens vs site screens, etc).
It will not be a WPMU plugin but a BuddyPress component…
boy you guys sure are rough on a noob… ofcourse I meant 1.0.3, it was late…
Thanks Mariusooms. I will give it a try. I thought it had something to do with my server, but was not sure where.
Thanks
…but it was when 2.8.2 just came out and no BP 3.0.1 release?
He means BP 1.0.3 I would imagine. That error has to do with your memory limit in your php.ini. Try adjusting it to 96M.
Take a look at the first few lines of file bp-core-avatars.php in the plugins/buddypress/bp-core directory.
/* Define settings for avatars. [TODO] This will eventually end up as admin configurable settings */
define( 'CORE_AVATAR_V1_W', apply_filters( 'bp_core_avatar_v1_w', 50 ) );
define( 'CORE_AVATAR_V1_H', apply_filters( 'bp_core_avatar_v1_h', 50 ) );
define( 'CORE_AVATAR_V2_W', apply_filters( 'bp_core_avatar_v2_w', 150 ) );
define( 'CORE_AVATAR_V2_H', apply_filters( 'bp_core_avatar_v2_h', 150 ) );
Currently they are not admin configurable yet, so keep not of the changes you make.
Did you try moving the themes to their proper locations and then try reactivating?
This can happen to some people when they do not have the themes moved out from under the /buddypress/ directory. It happens to me each time I upgrade BP and do not move the themes. For most people, however, this does not cause any issues.
Hey, is BP version 3 out ?
The only change I’m actually going to propose is this:
function bp_core_screen_general_settings_content() {
global $bp, $current_user, $bp_settings_updated, $pass_error; ?>
<?php if ( $bp_settings_updated && !$pass_error ) { ?>
<div id="message" class="updated fade">
<p><?php _e( 'Changes Saved.', 'buddypress' ) ?></p>
</div>
<?php } ?>
<?php if ( $pass_error && !$bp_settings_updated ) { ?>
<div id="message" class="error fade">
<p><?php _e( 'Your passwords did not match', 'buddypress' ) ?></p>
</div>
<?php } ?>
<form action="<?php echo $bp->loggedin_user->domain . 'settings/general' ?>" method="post" id="settings-form">
<p>
<ul>
<li><label for="email" class="settings-label"><?php _e( 'Account Email', 'buddypress' ) ?></label> <input type="text" name="email" id="email" value="<?php echo attribute_escape( $current_user->user_email ); ?>" class="settings-input" /></li>
<li><label for="pass1" class="settings-label"><?php _e( 'Change Password <span>(leave blank for no change)</span>', 'buddypress' ) ?></label> <input type="password" name="pass1" id="pass1" size="16" value="" class="settings-input small" /></li>
<li><label for="pass2" class="settings-label"><?php _e( 'Repeat Password <span>(leave blank for no change)</span>', 'buddypress' ) ?></label> <input type="password" name="pass2" id="pass2" size="16" value="" class="settings-input small" /></li>
</ul>
</p>
<p class="submit"><input type="submit" name="submit" value="<?php _e( 'Save Changes', 'buddypress' ) ?>" id="submit" class="auto"/></p>
<?php wp_nonce_field('bp_settings_general') ?>
</form>
<?php
}
If I can’t get this in core, how can I make sure these HTML changes persist after upgrades? Can I make a small plugin to do this?! I’m a real PHP n00b…
Well, you could either delete them from BuddyPress core (not a good idea), or unregister them in your theme’s functions.php file.
https://codex.wordpress.org/WordPress_Widgets_Api/unregister_sidebar_widget
Lisa-
The BuddyPress codex is in its infancy. But, there are a few gems you can glean.
https://codex.buddypress.org/developer-docs/custom-buddypress-loops/
Also, look in each of the component folders of the core BP files for a bp-xxx-templatetags.php file. You will find tags that you can directly use within your theme templates.
Do not install WPMU using SimpleScripts. Instead, you should manually install WPMU.
https://buddypress.org/forums/topic/404-error-in-front-page-please-help#post-16777
