Steps to Duplicate

1. Go to LT settings, check 'Set password', set 'Non-authenticated role' to any role but 'authenticated user'
2. Check 'Immediate login'
3. Logout and create a new user: user15
4. New user (user15) will now be "logged in" with whatever "role" you indicated above.
5. Check email, click the "verification" link.
6. You will be directed to the page and a message will be displayed saying: "You are logged in as user15. Change your password."
7. Logout.
8. Login as Admin
9. Check newly created user account (user15), you will see that they are still not "verified" and are still in the "Non-authenticated" role.

RESULT

In order for the user to fix this behavior, they must "logout" first, *then* click the verification link.
If they don't logout, they will have to generate a *new* verification link, then logout, then click it in their email.

EXPECTED RESULT

I would expect that the user account should be verified regardless of whether they are logged in or not.

Thanks.

Andrew.

Comments

danielw’s picture

danielw commented

I'm getting something similar, even without Immediate Login Checked.
The first [user:validate-url] does not work, and I have to click Re-Send Validation email for each user.

hunmonk’s picture

hunmonk commented
Status: Active » Closed (cannot reproduce)

@adf1969: guessing this is being caused because you haven't set the welcome email to use the validation url, instead you're using the password reset link that's in the welcome email by default. see LT help.

@danielw: the token works fine for me initially. i suggest trying a clean install with only LT and no other contrib modules, it's possibly a module conflict?

adf1969’s picture

adf1969 commented

@hunmonk: What special "validation url" are you talking about?
I read through all the LT "docs" (the README.txt and INSTALL.txt - not aware of much else except what is on the project page - there is not a "link" there to "documentation" so if there is some, perhaps that should be linked).

adf1969’s picture

adf1969 commented

@hunmonk:
I found the help. It is not on the project page, but is installed with LT.
For those looking, you can find it here: admin/help/logintoboggan

Checking for the "validation-url" now.

adf1969’s picture

adf1969 commented

@hunmonk:
I found the help. It is not on the project page, but is installed with LT.
For those looking, you can find it here: admin/help/logintoboggan

Checking for the "validation-url" now.

kalabro’s picture

kalabro
she/her
commented

Thanks! Token [user:validate-url] helped.

tommychris’s picture

tommychris
Primary language Hungarian
Location Budapest
commented
Status: Closed (cannot reproduce) » Closed (works as designed)

#6 works!

hargobind’s picture

hargobind
he/him
Location Austin, Texas
commented
Component: User interface » Documentation
Issue summary: View changes
Status: Closed (works as designed) » Needs review

I just ran across this as well. As @adf1969 stated in #3, there is nothing in the README.txt or INSTALL.txt about updating the welcome email with the new token. Per the comments above, I finally found this in the help page, but my feeling is that many developers only look at TXT files (and code) when installing a new module. (In my case though, I upgraded from D6 to D7 and never saw any mention of the token in UPGRADE.txt).

I'm reopening this issue to request the following paragraph (based on the LT help) be added to INSTALL.txt

Because this module completely reorients the Drupal login process you will probably want to edit the welcome e-mail on the user settings page (admin/config/people/accounts). Note when the 'Set password' option is enabled, the default token [user:one-time-login-url] will not remove the "Non-authenticated role" from the user. Instead, use the [user:validate-url] token which becomes a verification url that the user MUST visit in order to enable authenticated status.

stevecowie’s picture

stevecowie commented

I've got mixed feelings about this one. The fact that developers don't read the help isn't a compelling argument. However, I will certainly take a look at your suggested text in the context of INSTALL.txt so see if it's compatible with the level of detail already provided there. It feels a bit too much like straying into config rather than basic installation but I'll check.