This may be an incompatibility with either the pathauto or globalredirect module.

When a user creates an account pathauto creates an alias that looks like this users/efkrk3554kd or something similar it is randomly generated but you get the idea it is actually the temporary password given to the user that is being used for the last half. The problem is that this path should be created like this instead user/(username created by email registration).

What is happening is that when the user clicks the link in the email the arrive at the change your password page and after they do they are supposed to be redirected to their account page but the users/efkrk3554kd is no good so they get a page not found error. Also the user is being forced to this url by global redirect which does a redirect to an alias if it exists. So going to user/11 is the same problem because it just gets redirected.

Anyway if there is a solution to this let me know. I would love to use this module but pathauto and globalredirect are more important to me for this site so I won't be able to use email registration unless there is a fix.

Comments

Bilmar’s picture

subscribing

Christopher Herberte’s picture

Status: Active » Postponed (maintainer needs more info)

Tested, not happening with latest versions of these modules.
Please post process to replicate this bug.

bartezz’s picture

Version: 6.x-1.2 » 6.x-1.3
Priority: Normal » Major

My client reported the exact same situation for the activation emails that are send out. Version 6.x-1.3 is used but still encountering this issue.

Is this solvable by changing path alias patterns or other settings?

bartezz’s picture

Ok I've noticed this only happens after the account in question has been activated?!

greggles’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

My guess is that the mails that go out are using aliases that are generated with a bad username or something.

It would be helpful to know what tokens are in your registration mails and what other modules are on the site.

Marking closed for now because it's been a while with no concrete, simplified set of steps to repeat the bug, but if someone has a simplified test case please do post it.