BuddyPress.org

You should network activate BuddyPress.

This is so your user blogs can take advantage of BP functions. Most notably, the BuddyBar gets displayed at the top of each blog and your user avatars should use your BP one.

The Wire feature was deprecated with BuddyPress version 1.2. If you’d like to use the Wire, try installing the BuddyPress Backward Compatibility plugin and activating the wire feature: https://wordpress.org/extend/plugins/buddypress-backwards-compatibility/

The functionality of the wire – namely, the ability to leave short messages for other users – has mainly been replaced by the @-mention feature.

If you want users to have their own individual blogs, you’ll have to activate WP Network mode. If you want them to be able to post on your main BuddyPress blog, they’ll have to be at least Contributors. If you just want them to be able to post messages for others to see, then perhaps the status update feature will be enough.

@elizawhat; Your post made me think, and I checked our (not yet) live site, which does require email confirmation. Mostly I’m thrashing around at home with a local xammp installation, and can’t remember what I did to make the live one require email conf. The plugin linked to below should do it, although it’s not activated in our site..! Something in WP or BP lets you require email confirmation, but I can’t remember what.

https://wordpress.org/extend/plugins/bp-xtra-signup/

Buddypress runs as a plugin of a WordPress install, either WP single or WPMU / WP MS(WP 3.0)

If you have your WordPress install up and running then you need to upload or install via dashboard the BP plugin and activate, no further domain issues unless you have decided to run user blogs then you have considerations such as sub domains for the user blogs or sub directories and possible DNS issues if you want to use sub domains.

@themeanwhile – you can enable or disable the various components so if you want Activities only, enable that and disable other components. After you activate BuddyPress, go to the new BuddyPress menu item on the left column of dashboard, and go to

a) General Settings – these are your choices
Base profile group name:
Full Name field name:
Disable BuddyPress to WordPress profile syncing?: Yes No
Hide admin bar for logged out users?: Yes No
Disable avatar uploads? (Gravatars will still work): Yes No
Disable user account deletion?: Yes No
Disable global forum directory?: Yes No
Disable activity stream commenting on blog and forum posts?: Yes No
Default User Avatar – For users without a custom avatar of their own, you can either display a generic logo or a generated one based on their email address

b) Component Setup
Activity Streams – Allow users to post activity updates and track all activity across the entire site.
Enabled Disabled
Blog Tracking – Tracks blogs, blog posts and blogs comments for a user across a WPMU installation.
Enabled Disabled
bbPress Forums – Activates bbPress forum support within BuddyPress groups or any other custom component.
Enabled Disabled
Friends – Allows the creation of friend connections between users.
Enabled Disabled
Groups – Let users create, join and participate in groups.
Enabled Disabled
Private Messaging – Let users send private messages to one another. Site admins can also send site-wide notices.
Enabled Disabled
Extended Profiles – Activates customizable profiles and avatars for site users.
Enabled Disabled

I would suggest you set up a test install so you can check the features for yourself.

“Of course, activity filters, profile page, friends page, settings page, etc, would also need to be migrated to display in the backend.”
Why? If you want to make the BP Activity section private, you can add conditional tags for is_user_logged_in …

Since you’re using WPMU, BP just basically calls the WPMU user creation (see lines 320-321 in bp-core-signup.php). So, you’re going to have to mod the WPMU signup functionality to get the emails to send right.

Another temp option is to try the Welcome Pack plugin which allows you to modify the activation email that users get (I haven’t tried to take the link out, but it seems possible). That would solve the email they get.

Then, you could build a plugin to activate the users. Until then, you can just copy the activation key out of the database using phpmyadmin and browse to the URL yourself. Far from ideal, but the Flintstone way if you’re in a time crunch and need to get by until you can get a plugin.

You’ll have to know some coding to do this. This will get you started if you know some code.

You can add the hook to the following:
add_action( ‘bp_core_signup_user’, ‘join_all_public_groups’, 10, 3 ); //For WP
add_action( ‘bp_core_activated_user’, ‘join_all_public_groups’, 10, 3 );//For WPMU

Then, in the “join_all_public_groups” function, you can use this call to have them join groups: groups_join_group( $group_id, $user_id ); You’ll just need to loop through the list of groups.

I just re-installed my Buddypress site and switched from WPMU+Buddypress to just normal WP+Buddypress. The plugin here now appears to not work:
http://manojkumar.org/user-import-for-buddypress/

I manually uploaded it to my server and activated it and all seemed fine. But I can find no link to the plugin within my adm area. Maybe it does work fine but I can not find the link to where to upload users…. anybody have an idea?

I have a couple BuddyPress installs. The older of the 2 has received 150+ spam member registrations (and blogs) this weekend. All create members like bob45873675 and “Bob’s Blog”.

I have changed slugs, activated recaptcha and followed several blog posts on best practices. What’s interesting is they are somehow bypassing my registration page. I have required fields and have removed the “create a blog” from the registration page; but somehow they manage to create an account and a blog. I also receive “lost password reset” email notices for each account that is created, so maybe that’s a clue to where the issue is.

I was so fed up with it, I disabled registrations completely (only allowing blog creation by logged in users) — and I’m still getting new spam members and blogs (how is that possible??) This seems to be a pretty serious security issue that is different from previous “splogging”…

Vulnerability/hack in the registration or lost password, etc…?? I presume this could be WPMU not necessarily BP?

i have the same problem with wpmu 2.92 and bp 1.2.4.1
I have to deactivate buddypress in order to creat blogs.
Once blog created and buddypress reactivated, i am not able to link the blog with the group-blog plugin.

Does anybody have a solution ?

If you put it in functions.php you’ll probably need to do something like this:
function auto_login_bp() {
//Automatically log the user in
$user_info = get_userdata($user_id);
wp_set_auth_cookie($user_id);
do_action(‘wp_signon’, $user_info->user_login);
}

add_filter( ‘wpmu_signup_user_notification’, ‘auto_login_bp’ );

Although, even then it might not know the $user_id variable. So, you might have to add the code in my original post to the bp-auto-activate-user-and-blog plugin on line 170 or so. Although, that will cause the issues I mentioned above I think.

Thought I’d test this blog DB issue.

Chose an older test install with BP 1.2 – deactivated ALL plugins, removed all old BP folder and files, brought WPMU up to latest version from 2.9.1. Confirmed WPMU & blogs running correctly

Downloaded BP 2.2.4 Activated (doesn’t activate sitewide?!) enabled default theme but NO other plugins; visit site no blogs!

Check DB and confirm table dropped

Reset table rows as before, nothing still no blogs under BP & and of course no primary blog so can’t get back to dashboard normally

Feels as though 2.2.4 is built for WP 3.0? doesn’t feel backward compatible.

Not sure how this made it through any basic testing really to release candidate.

I would hope this release was retracted very quickly until the issue is resolved before others trot of and god forbid upgrade production sites with large numbers of user blogs and inadequate backups.

Oh! And it may be worth noting that BuddyPress used to appear in the Site-Wide Plugins list in WPMU…it now appears in the normal plugins list…which would in theory (I have checked it and I’m not going to try), that Users would be able to Activate/Deactivate BP via their Blog Admin (unless of course I hid it).

Geez!

Stephen G

Some thoughts;
– Assuming you don’t want others creating blogs in your installation, and you’re on WPMU, go to Site Admin > Options – under Registration Settings – choose ” User accounts may be registered.”
– Deactivate the Blogs component in admin dashboard – BuddyPress > Components Setup – under Blog Tracking – choose disabled
– Furthermore – https://codex.buddypress.org/how-to-guides/modifying-the-buddypress-admin-bar/

Thanks to Sarah Gooding, I found this plugin which mostly works with WPMU 2.9.2 and BP 1.2.3: http://www.thinkinginwordpress.com/2009/10/autoactivate-users-and-blogs-at-buddypress-signup/ Only problem is that it still sends the activation email despite the email already being active.

My hope is to incorporate the code from Andy so that it will work with both WPMU and WP and then make it so neither one sends the activation email.

If anyone has ideas why it’s sending the activation email in WPMU, I’d appreciate any help. Seems like it might be a priority issue, but I haven’t yet figured that out.

First of all, we may need more information. If what I suggest below does not resolve your issue, then please answer these questions: https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/when-asking-for-support/

The error message that you have posted is strange. BuddyPress does not have a file called bp-cores.php. You mentioned that you made some file modifications. Did you open up the file bp-loader.php? I would look in that file on line 19 to see if you accidentally added an “s” to bp-core. Line 19 should read:

require_once( WP_PLUGIN_DIR . '/buddypress/bp-core.php' );


If you see that there is an “s” but you are sure that you did not change it yourself, I would suggest deactivating then deleting BuddyPress. Then redownload BuddyPress and reinstall. Make sure your are downloading BuddyPress from this site

Finally, when trying to debug BuddyPress, always use the default theme and deactivate all other plugins. You need to isolate what is happening within BuddyPress.

@Dwenaus Thanks for this awesome plugin. Just one concern mate, it causes a JS error (the one that appears at the bottom left corner) on IE8. I made sure the script error comes from this plugin because whenever I deactivate or I am not on forum pages, the small yellow triangle disappears.

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; FDM)
Timestamp: Tue, 11 May 2010 15:09:01 UTC
Message: ‘length’ is null or not an object
Line: 12
Char: 7740
Code: 0
URI: http://aravig.com/wp-includes/js/jquery/jquery.js?ver=1.3.2

Can you please advise?

Cheers.

In the database (preferably with something like PHPMyAdmin) you can look at the table wp_signups under the column “active.” That’s WPMU. In WP you can look at the wp_users table. If I remember right, it just changes user_status.

I don’t know of a plugin that’s pulled this information. @boonebgorges has talked about a plugin that would do close to this including resending the activation email and clearing out ones that didn’t activate, but otherwise I don’t know a plugin that will do this.

M,
Yes, I thought of that. I installed the beta copy of WP 3.0 today and found that the users are still stored in the same places for a WP/BP install or a WPMU/BP install as they are separate. So, unless they’ve changed the core user signup calls, then we should be good, but I’ll be sure to test it.

It’s just too bad that there’s not some BP functions that I could just call like bp_core_creat_user(some variables) and bp_core_activate_user(some variables) so we didn’t have to dig in to figure out the functions that BP is already calling at registration. Maybe there is and I just don’t know it?