BuddyPress.org

1) By default, an email isn’t sent to the user because the user password is sent via plain text (not a good thing security-wise).

You can re-enable this welcome email by adding the following code to /wp-content/plugins/bp-custom.php (create this file if you don’t have one – be sure to add PHP open and closing tags as well):

remove_filter( 'wpmu_welcome_user_notification', 'bp_core_disable_welcome_email' );

2) Please post the avatar bug on BuddyPress Trac:

https://trac.buddypress.org/newticket

Login with the same credentials you use on buddypress.org.

3) WP-reCAPTCHA is not compatible with BuddyPress.

BuddyPress uses a different registration mechanism.

You might want to try one of these solutions listed here:

http://www.bp-tricks.com/tips_and_tricks/stopping-the-sploggers/

Did you disable new user registration?

I wholeheartedly agre with @andy. It’s an age old debate between making it as simple as possible to register and become a member and requiring some unique information that not only serves your purpose well but adds an extra layer to the process that fights spam.

We have been running our prod site since BP was in alpha (Nov ’08 – crazy, I know) but have had only 2 spam registrations. Both were from Russia and both seemed pointless. But we banned the domain in the WP backend and have had none since. We have not even changed our signup slug.

That said, we require 5 fields on registration, 3 are drop downs and we don’t allow blog registration (we’re building a community not a blog network)

On a side note: We ran reCaptcha flawlessly for 6 months. We disabled it as an experiment to see if we could avoid that extra step (plus reCaptcha words are damn hard to read) and have not had spam since. fingers crossed.

Which registration emails do you mean? The WPMU welcome email is disabled in BP; see function bp_core_disable_welcome_email() in bp_core_activation.php. It’s a feature…

“limit blogs plugin is set to 1”

That’s where it goes awry. Remember that your members already have 1 blog – even as a subscriber to the blog where your BuddyPress is installed, that is counted. So increase Limit Blogs to 2 so that in addition to main blog as subscriber or whatever role you made them to be, they can create one new blog for themselves.

https://buddypress.org/forums/topic/when-asking-for-support

I would like to bring up this topic again, as it is very crucial to the development of my website and I want to see if there have been any updates in the 10 months since this was posted. Right now I have blogs disabled, the main purpose of the site is to have different types of users interact on the site, and be able to search the site based the different details in their profiles..

Multiple profile types:

For my website I would like to have 4 profile types, all profiles have the same permissions, they just have different details listed in their public profile. These details can be defined during the registration process.

2-Stage registraion:

When the user decides to register, they are prompted with a page where they will select their profile type. Upon selecting their profile type, they will be taken to a second part of the registration process where they will fill in their profile information, each type of profile having a different form to fill in.

This should go along the lines of what Dev posted, minus the permissions. This is a huge hurdle for me to overcome, and if I can there will be one more addition to the Buddypress Community. Any help or direction is appreciated.

There’s not supposed to be any generated password upon activation in 1.1.3. No passwords are ever sent by email in 1.1.3. You may have missed something in the upgrade.

We had noticed that the welcome email includes a wrong password, perhaps because of different encryption between WP and BP. The password that was entered upon registration still works.

Note that in 1.1.3 the WPMU is disabled by default. To bring it back you have to remove a function from the core files.

@Harry

Yes, my Privacy Component works just as I described. It is an advanced beta available for testing. See this thread for more details: https://buddypress.org/forums/topic/buddypress-privacy-component-an-update/page/3#post-30574

@David

I wouldn’t give users the option to set it to friends only. Or at least… I would like the site admin to have the ability to disable that option.

In my Privacy Component, the site admin can choose to disable this feature.

But, to get back on topic, I agree that the best solution is the one that requires the brunt of the filtering to be accomplished through invisible, behind-the-scenes techniques. Requiring users to prove that they are members and not bots should not be the first line of defense. I think it is okay, even necessary for registration purposes. But that is a one time occurrence. After that, the system should do more of the policing.

Concerning your second link above, perhaps we could create a new CAPTCHA that could harness the collective intelligence of site members to solve the Unified Field theory.

Hi Andy, I think you are incorrect there. Spammers like to send spam. I am sure you get some in your email?

What is easier to get into a nice big community (without having to create a blog) and easily (?) send spam PM to all members of the community? You don’t even have to infect computers, as you can use the internal messaging system and you know most users will get the message as an email as well.

Hey, it saves them from email harvesting or buying ‘5 billion email addreses’ dbases as the community has already done this.

So, no, apparently (and this example that started this topic has proven this), it is possible on BuddyPress and it serves the spammers purpose, so disabling blog registration will not stop this. You can disable blog and user registration, but it might be hard to start a community that way..

Cheers, Harry

Hello.

I do have spam user registrations even with registration option set to:

[*] Only logged in users can create new blogs.

I understand this option to say that new user registrations are DISABLED but registered users may create blogs. Unfortunatly the “Register”-Button appears in the welcome widget with that setting — even though clicking it will redirect back to the homepage.

To disable the above option also disables the blog creation — which I do NOT want.

For an unkown reason I do see spam registrations (a couple per week) but it seems those users are not able to login and create blogs (or comment). I also do NOT get the usual notification mails for new user registrations.

It seems like a bug to me.

Looks like registration is disabled on your site. Do you have a guest username and PW I can use?

These functions should sort you out, garynagel:

function sv_check_current_users_blog( $active_signup )

{

if( ! is_user_logged_in() )

return $active_signup;



if( current_user_can( 'YOUR_CAPABILITY' ) )

return $active_signup;

else

return 'none';

}

add_filter( 'wpmu_active_signup', 'sv_check_current_users_blog' );



function sv_remove_create_blog()

{

if( ! current_user_can( 'YOUR_CAPABILITY' ) )

bp_core_remove_subnav_item( 'blogs', 'create-a-blog' );

}

add_action( 'wp', 'sv_remove_create_blog' );

You need to place these functions in your themes functions.php and replace YOUR_CAPABILITY with whatever capability you want to check for. You also need to have blog creation enabled. I’m using a slightly modified version of this to restrict users to maximum 1 blog, so I didn’t test this code at all.

The first function uses a filter to set the variable $active_signup to ‘none’ if the current user does not have a certain capability and for that user blog creation will be disabled. If the user has that capability the variable is not changed.

The second function removes the blog creation tab from the submenu. You probably need to modify the registration page as well.

Hope this helps.

Hi elemsee – great avatar!

If you disable blog registration through the wp-admin backend, where do you still see ‘create a blog’ etc options? We can create a Trac ticket to get this improved for a future version.

this is a great plugin. since I do not want anyone to create a blog with a group (so far users are only allowed to start their own group and blog registration is disabled): How could I – as admin – exclusively attach blogs to certain groups? Is there any way that only admins (of bp and not group admins) are allowed to create “group blogs”?

thanks,

Reiner