BuddyPress.org

Do non-BuddyPress specific emails get sent OK from your WordPress install? i.e. disable BuddyPress and get WordPress to send you a password reset email, or something.

White page usually means a PHP error. What’s in your web server error log?

I have the same problem. 50% of my users are marked as spammers
I think they don’t get the activation email, or it gets thrown in their SPAM folders..
It would be nice to have a functionality in WP to send them another email with activation link..

@dandelionweb


function my_redirect_activation_email()
{
return get_site_option( "admin_email" );
}
add_filter('bp_core_activation_signup_user_notification_to', 'my_redirect_activation_email');


Add this to wp-content/plugins/bp-custom.php or your theme’s functions.php file.

Try this https://buddypress.org/forums/topic/i-would-like-to-disable-email-activation#post-43474

Ahh okay, Erich! Thanks for the extra details.

It could be an issue with the email address that the activation email is sending from.

By default, the activation email tries to use the admin email option in WPMU.

If that isn’t set, it uses something like:

noreply@domain.com.

Which could be causing the activation email to go to the spam folder.

Try using the following plugin to set the email address:

https://wordpress.org/extend/plugins/mail-from/

I am having the same problem, no activation email.

Using BP 1.2.3 and WP MU 2.9.2

HELP!!!

Just to clarify, I’m not in favour of disabling email activation, either. The spam you’d be getting would kill your site.

However, the site I was doing this for does not allow users to post status updates in the conventional form. The site is an anonymous image sharing site. Users need to be registered to submit an image, but they needn’t be registered as themselves. Every user has the option of using [username]@domain.ext as their email address if they choose to stay anonymous.

Status updates are replaced by img tags to the uploaded image. Yes, they could spam in activity comments, but I guess that’s a risk that had to be taken. Until someone figures out how to use akismet on those comments too…

In all honestly, I wouldn’t recommend disabling email verification. In fact – you actually should not only use that, but use it with Gravatar to double verify members. My BP communities are brand new, in dev stages right now. I’ve already been subjected to spammers which is why I support use of Gravatars – because not only will your users be verified in your community, but globally and this is a big step in spam prevention.

If you want to customize the registration page, many of them can be through your theme framework. However, too much code will slice your page & overall framework right down the middle and break your site.

Does this also work with the BP Compatibility plugin or would there be an extra step? I have no problems getting this hack to work with single user WP + BP. However, when I try it with WPMU, it doesn’t work. I thought perhaps it was due to the fact that I’m using the Compatibility plugin in conjunction, but even when that is deactivated the hack isn’t working. Thoughts?

sometimes it depends on your host too. emails from my default bp install on dreamhost tend to make the junk/spam folder (yahoo, gmail, etc)

I have the same issue. Tried installing plugins, changing email to a “legit” one rather than the standard noreply@xxxx.xxx, tried sending through SMTP rather than mail()

Nothing works.

Most likely Hotmails spam filter reacts to the activation link, that would be my guess at least.

I have a lot of problems with BuddyPress user registration in general. It seems:

– no emails are sent to the user for activation

– there is no “forgot password” feature

– there is no ability to (re)send the user an activation link, either from the user or the admin’s area.

On the emails, when I create a new user or blog via the admin area, I get a notification email, so it’s not a setup issue with the mailserver. The server is my localdomain/localhost dev box anyway. No webhost involved.

Ugh this may seem a small part of BP % wise but it seems without these features it’s really not usable. What is the deal? Can this fundamental stuff really be missing/so buggy?? It’s hard to believe.

Extremely interesting but I’m a bit hesitant to do modding that needs to be at core. I’m hoping that Andy_P will see this! This have to get to core if it work! I’ll check the trac.

I’ve tried to sign up for your test website but I’m not getting any activation email.

I had the same problem a few seconds ago. A newly registered member didn’t recieved the activation email but was listed in WordPress>Backend>Users

I asked the user to check spam inbox twice but there was stil no activation mail

It would be great if admins could manually acivate such users or resent the activation email.

I’m getting several spammers signing up, I have the Anti Splog plugin (here) and the reCAPTCHA is turned on.

Email Activation is turned on.

AND I’ve blocked all of the emails on this list (here)

HOW ARE THEY GETTING THROUGH!

I have the same problem. users can register but they don’t receive a activation email and cannot login.

There was a thread which touched on the subject of plugin activation, I hadn’t really clearly understood the difference between ‘Site Wide’ and basic activation, or why sometimes activating a plugin using the plain link on left side actually activated the plugin sitewide placing the plugin into the list at the top of the page reserved for sitewided plugins that users cannot deactivate .

There is a configuration option in the plugin primary file hat should ensure that the plugin is activated sitewide regardless, it doesn’t always work and must be only half the issue, but I raised that on the other thread.

My approach to BP plugins is NOT to upgarde them automatically but manually deactivate, remove old folder to safe area outside doc root; upload new plugin reactivate using sitewide link, even though most BP plugins should or even ought to activate sitewide; there’s no reason for any general member to have access to BP or any of it’s plugins, and I don’t want to chance to having people access and deactivate a BP plugin

There was a thread which touched on the subject of plugin activation, I hadn’t really clearly understood the difference between ‘Site Wide’ and basic activation, or why sometimes activating a plugin using the plain link on left side actually activated the plugin sitewide placing the plugin into the list at the top of the page reserved for sitewided plugins that users cannot deactivate .

There is a configuration option in the plugin primary file hat should ensure that the plugin is activated sitewide regardless, it doesn’t always work and must be only half the issue, but I raised that on the other thread.

My approach to BP plugins is NOT to upgarde them automatically but manually deactivate, remove old folder to safe area outside doc root; upload new plugin reactivate using sitewide link, even though most BP plugins should or even ought to activate sitewide; there’s no reason for any general member to have access to BP or any of it’s plugins, and I don’t want to chance to having people access and deactivate a BP plugin

I found this mail sended in 2007 on wp-hackers, while searching for error message stuff at plugin activation

It seems to be be already the same situation in 2010… so devs, you know…

wp-hackers] Plugins : return proper error on activation faliure

Omry Yadan omry at yadan.net

Fri May 18 07:35:15 GMT 2007

* Previous message: [wp-hackers] List digest with unprotected emails

* Next message: [wp-hackers] Re: WordPress 3

* Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Some complex plugins may fail during activation (creating database

tables or what not).

currently there is no way for plugins to return an error signal + error

message in such cases: only thing they can do is to print the error.

this is problematic as the error does not fit well into the wordpress

admin page, and can also cause problems if for some reason the someone

tries to set an http header after the plugin was activated.

I suggest that we allow plugin to return error message back to wordpress

on activation.

Could someone please kindly turn this into a plugin?