BuddyPress.org

Login to your WordPress dashboard and click on BuddyPress on the left hand side. You will see a link called Profile Field Setup. This is where you create and edit your questions.

Hope that explains what you are looking for

Well, for those people who can’t/don’t want to update to the new version of BP, here’s the fix.

Make sure if you have a custom edit profile or registration template that you put brackets at the end of any multiselectbox field name that you’re using.

So, the following:

<select name="<?php bp_the_profile_field_input_name() ?>" id="<?php bp_the_profile_field_input_name() ?>" multiple="multiple">

would become:

<select name="<?php bp_the_profile_field_input_name() ?>[]" id="<?php bp_the_profile_field_input_name() ?>" multiple="multiple">

Then, you need to edit lines 400-421 of the BuddyPress core file: /buddypress/bp-xprofile/bp-xprofile-templatetags.php. It starts with case 'selectbox': case 'multiselectbox': and ends with break;

Replace lines 400-421 with code from here.

Note: this isn’t a very upgrade friendly way to deal with it, but if you’re stuck with BuddyPress 1.1.3 because of some custom written components, it’s the way to make it work.

ok, got this fixed….had to remove wordpress and install wordpress mu, registration issue resolved. hope this helps others

I have similar issues, and I have been pondering possible reasons this occurs.

I take the time to copy domain names that spammers com from, and add them to the mu-options as domains that are not allowed to create an account. I find that even after doing this, sometimes I get several more members with those email addys.. sometimes not.. the past week has seen a lot.

There was a time a few months ago when it was a known bug for this, but I am guessing it’s been fixed in mu by now – (I’m using 2.92 I think).

This is what I am thinking MAY be happening, and I’d love a way to update MU to close this loophole, if indeed it exists.

I am thinking that the spammers actually created a dozen or more accounts, and only activated one at a time. I am thinking that perhaps by the time I add the bad domain to the list of no-signups-allowed, they have already created several others – and simply activate them later.

If this is true, I would love for MU / Buddypress to do a check, when a member actually does this activation, and tell them sorry – the email domain is now on the bad list, and they can not activate.

Not sure if this is true, just a thought.

So is there a way to get the “welcome” or confirmation emails working WITHOUT WPMU?

I have an install running BP Version 1.2-rare & WP2.9.1

This is what I came up with:

place the function below into functions.php in your theme folder.

function sh_walled_garden()

{

global $bp;



if ( bp_is_register_page() || bp_is_activation_page() )

return;



if( ! bp_is_blog_page() && ! is_user_logged_in()  )

bp_core_redirect( $bp->root_domain .'/'. BP_REGISTER_SLUG );

}

add_action( 'walled_garden', 'sh_walled_garden' );

and this right on top of header.php (before the <!DOCTYPE… parts):

<?php do_action( 'walled_garden' ) ?>

The above makes all BP pages private, except the registration and activation pages. It also leaves all blog pages public. It’s a bit easier than editing all theme pages.

Boris

Paul.

I’m using WPMU 2.9 and the latest BP 1.2 release.. When I enable your plugin and sign up a new user the registration process goes fine, but no emails are sent out and thus registration is not possible. When I disable the plugin the registration emails do arrive, so something bad must happen somewhere.. I’ll try to pindown the problem

Have you tried to turn on users signups in your admin panel?

Site Admin >> Options >> Allow new registrations

@justin_k Wondering what your thoughts are on my situation: I run a site with a fair number of required, custom fields filled out on registration (class year, military branch, etc) and the site’s content is viewable only to registered members. We have considered using the FB-connect plugin given so many of our members are on and want to make things easy. I suppose they’ll have to be ok with potentially making their postings public (via their FB stream) but I’m most concerned about how to get the custom field filled out -> Do I redirect to yet another custom page that has just the non-FB connect related fields? Maybe I am biting off to much in the name of simplicity. Your thoughts are most welcome. Thanks.

You should probably look at the “Auto Join Groups” plugin:

http://brentandmary.net/2009/10/24/bn-auto-join-group-plugin/

It does what you want it to do, but automatically from the admin area.

Haven’t tested this in BP 1.2 though.

Might want to contact the dev of that plugin if it doesn’t work.

—

Also it is quite easy to modify DJPaul’s Welcome Pack plugin to auto-join groups as well.

See my post here:

https://buddypress.org/forums/topic/bbpress-and-buddypress-1#post-43925

—

Update:

Just came across a plugin called “BP Registration Groups”:

http://hardlyneutral.com/wordpress-plugins/

Purports to do exactly what you want, Bowe.

Nope not in the core, but you’re doing things like editing process_login.php and hacking the database and I’ll just end up adding pre-registration filters to enable user customization the “right” way (and include a default filter that changes usernames to ones that work with BP, as in Andy’s example code)

@mihaimihai ~ were your registration page failing on secondary domains, sub- domains/directories only or also in the root and when you say “multiple sites on different domains”..how are you mapping the domains, if you don’t mind me asking?

@mihaimihai

You might want to post this on Trac:

https://trac.buddypress.org/newticket

Login with the same credentials you use here on bp.org.

In bb-core.php -> bp_core_get_site_options()

if ( bp_core_is_multisite() )

$meta = $wpdb->get_results( "SELECT meta_key AS name, meta_value

AS value FROM {$wpdb->sitemeta} WHERE meta_key IN ({$meta_keys})" );...

buddypress doesn’t seem to be checking for the site id – so if you have multiple sites defined (on different domains) you can get incorrect results.

Fixed this in my MU install by adding this filter

add_filter('bp_core_get_site_options', 'bp_tweaks_bp_core_get_site_options');

function bp_tweaks_bp_core_get_site_options($options){

global $wpdb;

$option_names = array_unique(array_keys($options));

$option_values = $wpdb->get_results("

SELECT meta_key, meta_value FROM {$wpdb->sitemeta}

WHERE site_id={$wpdb->siteid}

AND meta_key IN ('".join("','", $option_names)."');

");

foreach($option_values as $v){

$options[$v->meta_key] = $v->meta_value;

}

return $options;

}

Yes Greg, lets do that. My testing site is here. The plugin will probably be added tonight. Anybody who wants to test logging in with their Facebook account is very welcome to until April 1st. The users database will eventually be deleted.

I have custom code that adds new members to a mailing list and synchronizes the real name to wp_usermeta etc. I’d probably have to add that code to the plugin somewhere, right? Or does the plugin feed the registration data back through the regular BP process as if it came from the signup form?

This looks really slick!

How does this work? Will users logging in with their Facebook login be added to the members database? Will Facebook logins be “mapped on” existing users or will it create double member registrations?

I’ll try on a test installation, but not sure how to test everything without creating test Facebook accounts etc…

EDIT:

Oops, should have read the plugin page:

# No user interaction is required – the login process is transparent to new and returning users alike.

# Existing WP users who connect with FB retain the same local user accounts as before.

# New visitors will be given new WP user accounts, which can be retained even if you remove the plugin.

This sounds too good to be true!

I’ve been getting pummeled with spam signups ever since the BP_REGISTER_SLUG stopped working throughout the site. I used R-A-Y’s idea of just having an .htaccess redirect. Just curious: If others have taken that approach, does it indeed cut down on spam signups?

If you put the following code in a plugin then this will disable activation, although the users will still receive an activation email. In any case, they will be able to log straight in and the new account screen will tell them that.

If someone wants to add this to a plugin and release it please do, but I haven’t tested it, so do that first. In the next version I will add an option to disable activation emails too.

function disable_validation( $user_id ) {

global $wpdb;



$wpdb->query( $wpdb->prepare( "UPDATE $wpdb->users SET user_status = 0 WHERE ID = %d", $user_id ) );

}

add_action( 'bp_core_signup_user', 'disable_validation' );



function fix_signup_form_validation_text() {

return false;

}

add_filter( 'bp_registration_needs_activation', 'fix_signup_form_validation_text' );

Theoretically, if we’d like to disable it, is there a way we can define it in wp-config or bp-custom?

We’ve got a workaround, but it involves changing a core file, bp-core-signup.php. We changed this line:

$wpdb->query( $wpdb->prepare( "UPDATE $wpdb->users SET user_status = 2 WHERE ID = %d", $user_id ) );

to set the user_status as 0 (activated)

$wpdb->query( $wpdb->prepare( "UPDATE $wpdb->users SET user_status = 0 WHERE ID = %d", $user_id ) );

Next, we changed a line in register.php, in a child theme, where we changed the conditional

<?php if ( bp_registration_needs_activation() ) : ?>

to

<?php if ( !bp_registration_needs_activation() ) : ?>

This solves the problem, but it involves modifying a core file. Any workaround for that?

Scratch that, fixed it. Made a mistake in my theme.

@ andrewnonumbers

Did you activate member registration in the admin area?