FYI, Welcome Pack 2.2 will include this functionality; I’m working with techguy on this.
techguy …I’ll be looking forward to your progress on this. As a side note…I’ve enjoyed your contributions around this community. Kudos
I think a lot of it is because its considered spam by most email hosts just as gmail, aol, etc. Can someone help create a fix for this? There has to be a way to change the way the emails are delivered from Buddypress.
Thanks,
eor
the problem same with my buddypress, new register never receive activation code from administrator
Hi
No, Welcome Pack won’t let you create or change which email address the activation emails are sent to.
Nice find Zachary. I wouldn’t recommend changing that file since it will get overwritten when you upgrade BP. Instead just use the bp_core_activation_signup_user_notification_to filter to change it to your email.
Figured this out, finally. Turns out that the file and function to modify was:
wp-contentpluginsbuddypressbp-corebp-core-filters.php
–>function bp_core_activation_signup_user_notification( $user, $user_email, $key, $meta )
Isn’t it redundant to have two functions so similar to each other? Both the above function and
wp-contentpluginsbuddypressbp-corebp-core-signup.php
–>function bp_core_signup_send_validation_email( $user_id, $user_email, $key )
are extraordinarily similar to each other. It’s kinda frustrating.
I’d consider developing a plugin, but perhaps I’ll wait for the first release of WP 3.0.
I have compared both the test server and the live server configs, disabled mod_security, checked different other settings and found NOTHING until I stumbled upon a pretty hidden error log of this client and there are a couple of different DB errors like [06-Jun-2010 10:46:25] WordPress database error Unknown column 'spam' in 'where clause' for query SELECT COUNT(ID) FROM wp_users WHERE spam = 0 AND deleted = 0 AND user_status = 0 made by require, require_once, do_action, call_user_func_array, bp_core_do_catch_uri, load_template, require_once, bp_get_total_member_count, bp_core_get_total_member_count
so its definitely a wordpress issue and not a server issue. here is a bigger part of the error log, just in case anyone has some feedback on this: http://pastebin.com/tx5gaEWG
gettign weirder and weirder:
the test site has these fields inside the wp_users table:
Full Texts ID user_login user_pass user_nicename user_email user_url user_registered user_activation_key user_status display_name spam deleted
the live site these:
Full Texts ID user_login user_pass user_nicename user_email user_url user_registered user_activation_key user_status display_name
After adding the two missing fields: spam and deleted, all is good 
Does anyone know when those fields were supposed to be added? I which WP version? or does BP add them? I’d like to figure out where this went wrong…
Any closer to getting this to work with mu?
Thanks,
eor
Yep, I just tried the Welcome Pack and you can remove the link and change the email that way and it sends to the user.
So, then you can just manually pull the activation key from the database using PhpMyAdmin or something and append it to a url like this: http://yourdomain.com/activate?key=KEY-FROM-DATABASE
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.
i don’t have the thread on hand but andy posted up a solution with filters/hooks to disable the email and change the user status
Just subscribing because I’m also interested in a solution to this.
@zlamczyk: I think we are trying to work on the same thing.
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/disable-activation-email/
I am getting spammed (bad) and they are simply using the activation email to approve themselves. My thought was just do a manual approval to either “activate”, “send activation email” or “delete from wp-signup”.
I have modified manual member approve for BuddyPress so I can see the signup table and manually approve members.
http://mattkern.com/wpmu-manually-approve-new-members-on-local-install/
I just need to stop the automatic sending of the activation email. Do you know how?
I’ve simply tried commenting out the following line in wp-core-signup.php to test, but it’s not working.
wp_mail( $to, $subject, $message, $message_headers );
This is the function; but for some reason the activation email still goes out.
@hnla and @boonebgorges: I found this plugin a while back and modified it to work with BuddyPress. Let me know if you need it still.
Anyone know how to stop sending the activation email? I don’t want to disable the activation function; I just want to stop sending the email automatically. I want to selectively send it. I figure I would just add this function to the manual approve plugin so I could either:
Manually Approve
Manually Send Activation Email
Delete the Signup
I’m getting killed with spam users (that are easily identifiable)
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/spam-blogs/
Also; each “blast” of spam users/blogs appear to come from different IPs, but the username always has a 7 digit number pattern after a random name. They all appear to come from “.info” email registrations.
These registrations are bypassing the public registration form requirements somehow, but I believe they are legitimately activating their account (since I’ve had delays after disabling the registration form). There are entries in both _users and _signups tables that match.
Hope this helps if anyone else is having this issue. I’m open to any temporary solutions for this particular pattern, but more importantly is there a good way to solve this long term?
Is there a way to manually approve members? Maybe some step in between that would allow a manual send of the account activation email?
ok guys. figured it out. this killed me today. godamighty.
needed somebody to send me link to this resource:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/email-notification-not-working/?topic_page=2&num=15
anyway, there’s some kind of mail issue for ppl hosted at bluehost. you have to get the Mail From plugin:
http://code.andrewhamilton.net/wordpress/plugins/mail-from/
and then everything works fine.
just heads up for ppl that have this issue in the future.
yes, receiving email from WP (comment notification).
Disable BuddyPress. Do you get any emails from WordPress on itself? e.g. user registration, comment notification, etc.
i just deleted the plugin. then reinstalled. tested with a different email account.
is it possible that there’s something wrong with my server that’s preventing these emails from being sent?
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.
@crashutah thanks a lot man for your responses and information. I’ve noticed that there is some differences indeed between single and MU handling the whole registration, activation, and log in processes.
I tried this piece of code (in my functions.php after the disabling activation and email bits) however it game me some weird behavior and my backend became non functional. I probably missed something (used the code as is while I needed to modify) or maybe one of my other plugins is causing misbehavior? I have auto redirect to profile on login plugin, and branded login plugin activated.
Cheers.
