I have been running BP in Production since well before the 1st alpha release on the same url with the exact same registration slug AND requirements. Nothing is protecting on my site any more than a standard install – no captcha, etc. I can count on my hand the number of spam attempts to register. They are so few, I just delete them and use BanHammer once they try.
How? We have a specific (albeit small) set of required registration fields to fillout. That’s all. I love siple and fast registration as much as the next guy but, unless you want to enforce email address verification and a bunch more, those are your real options.
Changing the slug will work until it doesn’t …which won’t be very long. Consider how that spammer found you in the first place…with a bot – not by randomly coming across your site.. and just like in the matrix, the bots will find you again. 
keep in mind, it’s not “broken”. We are debating the merits of one way versus the other. There is not an email as you suggest in BP/WPMU just Activation. most sites that I join these days do not send their passowrds on signup, usually activation emails. You could always write a plugin that sends the password.
Schwoomba,
Actually figured it out the other day – I think.
1)Copy registration.php from buddypress parent theme into your own theme.
2)Paste this into registration.php underneath line 25 (might be different) :
w<label for=”country”><?php _e( ‘Country’, ‘buddypress’ ) ?> <?php _e( ‘(required)’, ‘buddypress’ ) ?></label>
<?php do_action( ‘bp_country_errors’ ) ?>
3) Then install firebug as a Mozilla add-on.
4) Go to a site who’s registration page has a drop-down list that you want.
5) Use firebug and right click on the element you want and say “inspect element”.
4)Say Copy HTML
5)Then past it into your registration.php under the the lines you pasted in step 2
Should work.
You could do this with gender , birthday etc. = Just change “country” in step 2 .
Actually the first time that I’ve given some advice
Hope it helps.
Yes, I am running BP 1.2 beta with single-user WP, not WPMU, and it’s a fresh install of both. It’s not a huge issue, I just think philosophically that after a user signs up for a service, they should receive a confirmation email that includes a link to the site, along with their username and password, even if they chose them themselves. This, after all, is what happens with BP in WPMU, although the latter does include the activation link which I assume has been deemed to be unnecessary in the single-user WP version.
I know from experience that users forget their logins over time, and while they can use the “forgot” link on the site, I think having an initial registration acknowledgment saved in email would be beneficial for some users. Also, it gives the site publisher an opportunity to send a greeting message to each new subscriber.
So…any thoughts on how to make this work for me, or whether it will be fixed in the next version of BP? Thanks.
@snark didn’t realize you are single user WP so no activation email
If you reset your password it doesn’t send you a new password, you log into the site with a link to reset it.
There is not going to be an email sent with username and password (not really necessary given they just chose one) There is, in fact, an Activation email. Did you not receive that?
(Recall the annoyed furor over site devs complaining that their users had to wait for an email with their password. Consider that addressed!)
@snark You forgot to mention the Activation email. Is your new user not receiving one? I just did a test registration and immediately received an email. While I agree with @Peter that plain text isn’t so bad but I also think it’s not so necessary to send the password the person literally just chose. The always have the Forgot Password link if they forgo it seconds after the fact. No real need as I see it to add a filter.
@snark, I simply removed the function bp_core_disable_welcome_email() from bp_core_activation.php. But then the password in the welcome email is wrong, as discussed here. Haven’t been able to come up with an explanation/solution for that… 
I agree. So any new ideas on how to get that filter-killer function to work? Thanks.
Here’s the rationale behind disabling the welcome email as quoted in bp-core-activation.php:
* Since the user now chooses their password, sending it over clear-text to an email address is no longer necessary. It’s also a terrible idea security wise.
I’m going to sway a little to Peter’s side and say that BP should leave this option to the site admins. I actually think there should be more options for the administrator on a fresh install.
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).
That makes absolutely no sense. If you use the forgot password feature, the password is sent via plain text as well. Why is that OK and sending a password upon registration not?
Most big sites, Facebook, LinkedIn, newspapers, have no problem sending passwords via plain text. Online security is always a balance between security and convenience.
Buddypress is a social network. It’s not a banking website. If you start using credit card payments or paid membership, those scripts usually come with the own security.
Who is going to steal a password to someone’s account on a blog network? Has that ever happened? What would they do with it?
Just my 2 cents. Flame away…
Still not working. I did find the filter itself in the file /plugins/buddypress/bp-core/bp-core-activation.php:
add_filter( ‘wpmu_welcome_user_notification’, ‘bp_core_disable_welcome_email’ );
I suppose I could just delete that line to remove the filter, but then every time BP is updated it’ll probably get overwritten and I’ll forget all about it. Not sure why your filter hook didn’t work. Any ideas?
Thanks a million for your help — I really appreciate it.
Re #1:
Sorry I forget that you need to hook the filter to an action.
Try this:
function snark_reenable_welcome_email() {
remove_filter( 'wpmu_welcome_user_notification', 'bp_core_disable_welcome_email' );
}
add_action('init', 'snark_reenable_welcome_email');
The file is /wp-content/plugins/bp-custom.php
Re: 1) I tried this and it didn’t work (no error, but didn’t fix the problem). What directory exactly should the bp-custom.php file be put in? I tried it in two places —
/wp-content/plugins/bp-custom.php (where you said to put it, though that seems odd)
and
/wp-content/plugins/buddypress/bp-custom.php
— and neither worked.
Re: 2&3) Will do. Thanks.
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/
I don’t know about simplescripts, but go here ~
yoursite.com/wp-admin/wpmu-options.php
and you’ll see the option under Allow new registrations.
i’d imagine that simplescripts is using WordPress MU version 2.9 so you need to navigate here yoursite.com/wp-admin/wpmu-options.php and you’ll see the option under Allow new registrations.
I might make a new website where I allow registrations and disallow blog creation.. Put one HUGE widget on the frontpage with the names of the new users and call my site:
http://www.goodbabynames.com
Put it full with advertising and BAM! I’m rich..
Thanks for this awesome idea!
Update: Here is how we use a custom field to look up a group and return it’s ID to create a custom query stream:
// passes MyClass scope into ajax query for custom Class Year activity filter
function bp_my_ajax_querystring_activity_filter( $query_string, $scope ) {
global $bp, $wpdb;
if ( $scope != 'myclass' || !is_user_logged_in() )
return $query_string;
$args = array();
parse_str( $query_string, $args );
$args['object'] = $bp->groups->id;
// get user's class year and generate slug (BN naming
convention is usma-yyyy for class groups)
$slug = "usma-". bp_get_profile_field_data( array('field'=>
'Class Year', 'user_id' => $bp->loggedin_user->id));;
$groupid = BP_Groups_Group::get_id_from_slug($slug);
$args['primary_id'] = $groupid;
return http_build_query( $args );
}
add_filter( 'bp_dtheme_ajax_querystring_activity_filter',
'bp_my_ajax_querystring_activity_filter', 1, 2 );
Every new user selects a graduating Class Year e.g. 1987 upon registration. They are auto-joined to a Class group with the naming convention ‘USMA YYYY’ (the slug is then ‘usma-yyyy’
So the $slug var is generated off a lookup of the logged in user’s Class year field and then the slug permits lookup of the Group ID. Of course, sticking to a naming convention is how this works but the concept is pretty simple.
You could easily have a custom field (required or voluntary) that provides a starting point via it’s values for custom Activity filtering. TIP: Stick to drop-downs and check boxes in order to control the values fed to the $slug function.
@ yudhister, before you install 1000 plugins to have what you want, read this:
https://buddypress.org/forums/topic/how-to-add-custom-usermeta-to-registration
Actually i want add fileds in blog registration form.So add tow fields Music Genre and Country
fields using buddypress .After that i created new signup. Except above two fields values all values are saving the wp_signups table .But how to save the Genre and country values.
Kindly give me as suggisions.
No one has any suggestions?
Hi, katemgilbert, in more detail, after login, you go into http://sitename/wp-admin/admin.php?page=bp-profile-setup. And then, you can customize the registration and profile form that you want.
Login to your WPMU admin area and navigate to “Site Admin > Options”.
There should be a header saying “Allow new registrations”.
