BuddyPress.org

Wow, that’s a really impressive setup you got going at http://kodingen.com. Thank you for posting this ~ I wouldn’t know where to start with hiphop yet, but I registered and noticed that the activation email is missing a backslash. I had read this statement from @rasmus and figured it’s performance gains and high scaleability would also depend on a series of other configurations like memcached and sql optimization. But something like this could prove to be as Rasmus puts it, escape from ‘framework soup’. Although wordpress.com seems to be running top notch on top of Nginx, but I’m sure they got all kinds of hardware and configuration tweaks going on.. // all the same thanks for for the experimenting and good luck with it.

I’m somewhat at a loss as to why people debate this issue or try and state it’s a WP issue as logically that doesn’t make sense?

As jfigura posts this is an inherent problem, I have it on a production install and it must be hugely confusing for users, and yes the only approach so far has been to modify the text and remove the WP password from the confirmation emails.

Further testing points to the initial blog registration as being possibly the issue:

Clean install of WP MU 2.9.1 & BuddyPress 1.2 no significant further plugins activated.

Test Condition 1:

WP MU with BuddyPress disabled – admin options -> Allow New Registrations ->’Only user account can be created’

Register new user

Receive confirmation email of new registration along with Activation key

Activate registration

Receive second email with account username and pass

All as expected!

Test Condition 2:

WP MU with Buddypress activated – admin options for registration still set as ‘User Account only’

Register new user

Receive confirmation and activation key

Activate registration – screen message stating ‘you can now login with user name and password you set’

No further emails sent!

Test Condition 3:

WP MU BuddyPress still activated – admin options -> Allow New Registrations -> ‘Enabled. Blogs and user accounts can be created.’

Register new user as well as a blog!

Receive confirmation and activation for account and new blog

Activate registration – screen message ‘you can now login with password you set etc etc’

Receive further email from WP! (copied below)

Dear User,

Your new *********.co.uk Blogs blog has been successfully set up at:

http://eggs.********.co.uk/

You can log in to the administrator account with the following information:

Username: eggbert

Password: 5f112917

Login Here: http://eggs.**********.co.uk/wp-login.php

We hope you enjoy your new blog.

Thanks!

–The Team @ ********.co.uk Blogs – Sent via Site Admin options email

So having new accounts and new blogs enabled at initial registration triggers the sending of the ‘Welcome Email’ noted above.

clearly this is confusing as it contains the WP generated password.

Why is it that BP registration doesn’t disable / override the WP registration completely? To my mind this IS a BP issue, but I may very well be wrong on that score as I don’t profess to have a deep understanding of the core coding involved here.

On a sidenote:

Testing this and the slightly odd behavior of ‘Allow New Registrations’ where option for ‘only logged in users can take a blog’ actually seems to prevent all registrations. It occurred to me that on a social community ,and from our experience, blogs are not necessarily what users register for and that I would prefer the option to have a blog be only available for registered users from their account options. what actually happens is that registration is disabled completely! Not the effect I desired. I realise this IS a WP MU issue but is simply daft behavior and that set of options needs to be re-worded to be a lot clearer as to what it really does.

It would be great to be able to restrict blog signup to users already with account set up and remove, completely, the option to take a blog on initial signup, I have done this by simply scripting out the option / section for registering a new blog in BP register page but feel it’s not the best approach?

https://trac.buddypress.org/browser/trunk/bp-core/bp-core-activation.php#L79

There are two ways for this email to still get sent:

1.) Your active theme does not have either /register.php or /registration/register.php in it.

2.) You are an admin that has just added a user to your site.

If either of those things are true, the email will get sent out.

If you are hard pressed to make this issue go away, try adding this to your functions.php or bp-custom.php.

/* Unhook BuddyPress wpmu email blocker */

remove_filter( 'wpmu_welcome_user_notification', 'bp_core_disable_welcome_email' );



function block_wpmu_email() {

if ( is_admin() && $_GET['e'] )

return true;



return false;

}

/* Rehook custom function */

add_filter( 'wpmu_welcome_user_notification', 'block_wpmu_email' );

The above routine doesn’t help us test this issue any, but it does stop the email from going through unless you add a user yourself.

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.

@snark didn’t realize you are single user WP so no activation email

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…

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.

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…

Is it possible to have the welcome email include the RIGHT password? (i.e. the password that was entered upon registration)

Any idea how?

I’d like to know this as well. You could probably put this on activate.php somehow.

Also the standard WPMU welcome email is sent on first login. That works via a function in wpmu-functions.php:

function wpmu_welcome_user_notification($user_id, $password, $meta = '') {

global $current_site;

...



wp_mail($user->user_email, $subject, $message, $message_headers);

return true;

}

I don’t see a hook in that function. It’s called/triggered from function wpmu_activate_signup in the same php file.

wpmu_activate_signup is called from function bp_core_screen_activation in bp-core-activation.php.

Perhaps you could add a redirect there to the mandatory extra fields? There are already some if statements there, one with this:

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

You could add your own? Just guessing, wouldn’t know what it would look like…

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.

Could this also lead to the wrong passwords in the welcome email?