If LoginToboggan is installed it seems the the one-time login goes directly to the user account. No one-time login button and no redirect to account edit to change the password.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | lt_redirect.patch | 349 bytes | iva2k |
If LoginToboggan is installed it seems the the one-time login goes directly to the user account. No one-time login button and no redirect to account edit to change the password.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | lt_redirect.patch | 349 bytes | iva2k |
Comments
Comment #1
iva2k commentedI have the same problem. Quick rework is to fill in the LT option "Redirect path on Confirmation:" to "user/%uid/edit" or "user/%uid/password" if using password_policy & password_tab modules.
Comment #2
iva2k commentedAlso, there is a fix that can be done in the code (see the attached patch)
Comment #3
iva2k commentedComment #4
iva2k commentedOne more priceless thought here:
In the presence of password_tab, logintoboggan (as well as any other similar module, including core user) should by default redirect to user/%uid/password. Then core should provide two paths, user/%uid/password for all modules that intend to change password, and user/%uid/edit for all modules that intend to edit user profile, other than password. Then, if there is no separate password tab, core should default to profile.
Just more of misplaced 2 cents.
Comment #5
hunmonk commentedi don't advise the solution in #2 -- the solution in #1 is clean and effective, and won't cause upgrade headaches.
LT takes over the registration/validation process as part of it's job. setting "Redirect path on Confirmation:" to a value you desire is part of proper configuration of the module.