BuddyPress.org

As always, https://buddypress.org/forums/topic/when-asking-for-support

A you redirecting to the buddypress pages? You shouldn’t use the standard wpmu register and activation. I remember Andy saying that he fixed this, but I guess it isn’t working like it should yet.

Try this.

http://mirlo.cl/how-to/fix-for-signup-and-activation-pages/

I think I ended up commenting out the email notification before first activation on a live site. I then added it back. If I remember correctly you also have your activity stream somewhat spammed so that might be another thing to look at

I’m having the same problem. Sometimes the activation key is also not valid.

right now, i just registered, had an activation email,

(btw, the email title is: [BuddyPress Testdrive] Activate http:// )

activated, but then my password is not working… requested new password to access.

in the wp-admin, the recent Comments block, each comment url point to the wp-admin/index.php file… no real usage… rofl

the adminbar in the wp-admin is hovering the original from wpmu… and i’m dyslexic… rofl

You are using outdated versions of both WPMU and BuddyPress. I urge you to upgrade.

There was a bug in some previous version of BuddyPress to do with the wrong link being put on to the activation emails, but without knowing exactly why people can’t activate their accounts (i.e. do they get the emails? Does the link work? What happens?) it is tough to provide specific advice.

Yes, that is the next step I’d suggest.

Is this a localhost development install or a remote, hosted install? If hosted, is it a live site that used to work but is now experiencing this issue?

Have you modified the standard .htaccess file that WPMU automatically creates on new installs? This could be done manually or via some plugin that you’ve recently installed and activated.

@MrMaz

Unable to receive activation or lost password emails.

Although WPMU now tells me everything is installed and working I’m not able to register using the buddypress frontend. I found a reference in a forum suggesting that any plugins with ‘-‘ in their name can cause the error I’m seeing.

From my log:

Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInternalRecursion’ to increase the limit if necessary.

I’m still getting this after deactivating buddypress-links though so may be more of a buddypress general support quesiton. Any ideas?

you are most welcome

Well,just go to your current theme and edit registration/register.php,remove the line saying “You have successfully created your account! To begin using this site you will need to activate your account via the email we have just sent to your address”.

you will see it somewhere written under

‘<?php if ( ‘completed-confirmation’ == bp_get_current_signup_step() ) : ?>’

Remove that.

Better I just suggest to remove the avatar uploading step,as the account gets already activated and the uploaded avatar(the second screen of registration)(which earlier were used at the time of activation will not work)

so,If you are using un modified default theme,you can remove the code from line 215(where the if starts) to 276,where the if ends safely.

Please note,The avatar uploading step at registration will not work,so just remove that step.that’s it.

Thanks

Brajesh

I’m seeing this, too. I just tried a fresh install of WPMU (2.8.4a) and tested Dashboard > Users > Add User (worked fine, email arrived intact).

After installing and enabling BuddyPress 1.1.1, doing the same thing to Add User results in a borked email:

Hi,

You've been invited to join 'WPMU Test Blogs' at

http://myserver.ca/wpmu as a subscriber.

If you do not want to join this blog please ignore

this email. This invitation will expire in a few days.



Please click the folowing link to activate your user account:

%s

The last %s isn’t being substituted by the activation link.

Previous to BP 1.1, all user registration was dealt with by WordPress, so it’s technically correct to point people towards existing WordPress/MU resources and forums for help.

Since BP 1.1, however, BP changes the new account confirmation/activation email – because on the standard BP 1.1 signup page, the user can pick their own password. And of course, it’s a security issue if we were to somehow send their (encrypted) password back to them. So BP 1.1 overrides the standard WordPress MU email so it doesn’t include the password text.

But, the activation link is part of WordPress. Yes, the BuddyPress default theme uses this behaviour too – but it calls the WordPress code.

I’m still lost. I also don’t really have time to look at this until the weekend sometime. Could you help me again please?

Yep, I go to the main blog via Users menu (not site admin>users) and…

Could you give me a sample link (feel free to cut your domain off the beginning), i.e. http://example.com/how_to/get_to_this/page. I’m being a noob and can’t see it

...EXCEPT the email with username & randomly generated password that should replace that activation email shown above. (I'm thinking this is a wordpress email? Not sure.)

Correct. Welcome Pack doesn’t (or shouldn’t) touch the activation email, which is why this issue is so weird-sounding.

You ARE aware since BP 1.1, if a new user registers via http://testbp.org/register, they are able to pick their password and as such it isn’t emailed to them? (Though they still get a confirmation/account activation email)

When I use the site admin>users method it doesn’t engage with Welcome Pack, which is the same thing that happened in my previous version of BuddyPress. The activation email gets killed there too, just tested that.

Yep, I go to the main blog via Users menu (not site admin>users) and input the username and email address, select skip confirmation email, send. I get all of the notifications welcome pack sends out EXCEPT the email with username & randomly generated password that should replace that activation email shown above. (I’m thinking this is a wordpress email? Not sure.)

The weird thing is when I do the same process from a sub-blog everything behaves the same except I DO get the email with the username & randomly generated password in addition.

In case it helps here’s what happens over 3 tests from each main & sub blog dashboards:

MAIN BLOG DASHBOARD:

1. Broken activation email – came first all 3 times

2. Then these 3 come, random order each time:

Welcome pack welcome email

Welcome pack friend invite email notification

Welcome pack group invite email notification

SUB BLOG NEW USER:

1. Broken activation email

2. Then these 4 come, random order each time:

Account is setup email with username and randomly generated password

Welcome pack welcome email

Welcome pack friend invite email notification

Welcome pack group invite email notification

Thank you for working on this problem!

BP1.1.1, Welcome Pack 1.41

In case it helps, see the activation email that I get below, it gives up at the link. This message gets sent even though I had skip activation email selected, and no email stating username and password is sent.

Hi,

You’ve been invited to join ‘CoP Literacy Network – Sandbox’ at

http://copgardensandbox.com as a subscriber.

If you do not want to join this blog please ignore

this email. This invitation will expire in a few days.

Please click the folowing link to activate your user account:

%s

I am also having problems with Welcome Pack. BP1.1 & BP1.1.1 same problem, WPMU2.8.4a. Fatal error on activation of the plugin, though it mostly works here’s what I get:

Register a user as admin in dashboard, select “skip confirmation”. Sends out confirmation anyhow, and email dies at activation link. I do get all other welcome pack emails except:

If sent from main WPMU blog don’t get the email that states username & pw

If sent from sub blog do get the email that states username & pw

Both tests have the same confirmation email that shouldn’t be sent that dies at activation link.

See https://buddypress.org/forums/topic/can-buddypress-activation-emails-be-turned-off too.

THis is a WPMU thing. I believe this behaviour has changed in BP 1.1.1. I strongly suggest you upgrade your install regardless.