BuddyPress.org

@v_andreev

Did you try closing the window or tab, and then simply clicking the email link again?

I am posting this here because it might solve part of the problem and it worked for me: I found this <a href "https://buddypress.org/community/groups/buddypress-pending-activations/&quot; While it does not solve the issue of members being able to approve themselves, it does allow the ability to resend an activation link (email) and to manually approve members in the Que. It works with WP 3.1.3 and BP 1.2.8. I hope this helps the scores of people desperately seeking admin approval of new user registrations.

I found this <a href "https://buddypress.org/community/groups/buddypress-pending-activations/&quot; While it does not solve the issue of members being able to approve themselves, it does allow the ability to resend an activation link (email) and to manually approve members in the Que. It works with WP 3.1.3 and BP 1.2.8. I hope this helps the scores of people desperately seeking admin approval of new user registrations.

`Warning: Cannot modify header information – headers already sent by (output started at /path/wordpress/wp-content/plugins/buddypress/bp-themes/bp-default/registration/activate.php:3) in /path/wordpress/wp-includes/pluggable.php on line 897`

As @r-a-y suggests, in my experience at least, that kind of error is almost always malformed PHP files — trailing spaces, unclosed brackets, stuff like that. If you’ve pasted functions into your functions.php or bp-custom.php, look there first, then any other template files you’ve edited.

Don’t use @r-a-y codes

@mikey3d – Is that a general recommendation?

I did say it was test code. Looks like you have whitespace issues in your /registration/activate.php. Delete any trailing whitespace from the beginning of that file.

eg.
`   -spaces – <?php` – Delete that trailing space!

Your htaccess rewrite rules look like it will interfere with querystring variables.
eg. example.com/my-page/?variable=my-test

The only way I was able to surmount the same issue (emails not being sent, i.e. new user notification, password reset emails) was to disable the following plugin:

“BP Disable Activation”
https://wordpress.org/extend/plugins/bp-disable-activation/

Once I disabled this plugin, the missing emails flowed again.

As such, I returned the site to its default state of requiring new users to confirm their accounts.

Yes it already exist: https://buddypress.org/community/groups/bp-disable-activation/

Oh ok ; yes I’m with you now, usually think of duplicate content from the perspective of www and non www it’s really googles issue though, the url refers to the same thing ultimately.

However google trawls links in a page and the links are trailing slashed, from the perspective of inbound links that might not have the trailing slash added it could be an issue I guess.

“and it does support sending email and has for a few new user registrations.”

So it has actually *sent* mail.

Edit:

Your server is not the problem. Not entirely anyway. I signed up to your site and got two emails – one with an activation link and one confirmation email. Exactly like I am supposed to.

So your problem is *not* the server is not sending email. The problem is some of the people signing up are not getting them. Which means it’s mostly on their end. You can do a reverse dns entry, like @hnla stated above, but really that’s all you can do for some places like Hotmail & Comcast.

Not sure why this is a problem? the trailing slash is in essence a nicety in that it means one is asking for a directory rather than a file and it helps the server otherwise the server first searches for a file named /foo before checking if /foo is actually a directory /foo/ but you’re right although all my test sites links terminate correctly / I can manually write the url without and it’s not added but it doesn’t cause any issues – however I may well be missing the point of what you are explaining

Had exactly the same problem as mentioned by the OP. To repeat:
1. User creates account.
2. Clicks on Activation Link in email.
3. Gets taken to a page that says Activation Successful. You can now Log in
4. Logs in (login is successful) but is taken to a page with a message, “Please enter a valid activation Key” with an empty field below.
5. If the user ignores this, he/she can start using all the BP features.
6. This message appears only the first time they log in. Doesn’t appear on future logins.

Have upgraded to the latest WP 3.1.3 and BP 1.2.8 and yet the problems persists. Any ideas.

Thanks

Yes I had the same problem. It appears the activation link is ONLY being sent to people with GoogleMail accounts.

I also experienced this problem. It seemed that the e-mail’s were only being sent to Google Mail Accounts. To temporarily resolve this I just turned account activation off.

ok try this :

use this plugin to manually active users that are not activated yet : https://wordpress.org/extend/plugins/wp-activate-users/

and use the below code in your functions.php .to disable email activation.

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’ );

Firstly check your filter, choose alphabetical order and see if all members show, and also if your site require email activation, you will see some members under manage users but not in members directory because their email is not verified yet. hope this will help.

regards

I’ll try to help a little….
1. Buddypress by default sends an email to user for activation. Your theme may not be pulling the “ and all the code thereafter. Check to see if switching to buddypress default fixes that.

2. Yes you can create your own login page. The easiest was is using a plugin like Theme My Login, though you could always do your own custom stuff.

I also had this problem and went through a deep analysis.

The issue stems from the fact that Bluehost requires that the email be sent from an account that exists on the system. They do this as an anti-spam technique and they require this even if the mail is originating from within the system.

Enter WordPress. PHP uses a mail function mail(). WordPress maps this to wp_mail() and pretty much everyone uses the wp_mail for the plugins within WordPress. This makes sense as it allows customization of WordPress mail at a relatively low cost of performance.

Enter Buddypress. Buddypress places a filter upon wp_mail() such that all email originate from the user ‘noreply’ on the domain such that end users don’t reply to the notifications. Sounds cool.

But remember that Bluehost does not allow email to be sent from non-accounts and that’s the catch.

Using a foreign SMTP does not work for Bluehost blocks those ports. Using local SMTP will work but you need to provide the right setup and credentials. Finally, using mail-from plugin works since it filter’s the Buddyhost filter changing the email from address back to a valid Bluehost email account.

Hopefully, this explains what is happening and you can choose which strategy you want to use to fix the problem.