When you are logged out and you want to request a new password you will be redirected to the login page, with just a little message in the top window that says "Further instructions have been sent to your email address." In my opinion it's illogical to redirect to the login page, because the user can't log in, and the e-mail doesn't provide you a username and password, but a link, so you never need the login page in this scenario. I rather see a full page explanation about receicing an e-mail with a link to login.
Redirect to homepage instead of user login page.
None
| Comment | File | Size | Author |
|---|---|---|---|
| #27 | 2409657-27-password-sent-front.png | 42.35 KB | ressa |
| #25 | 2409657-25.patch | 565 bytes | anushrikumari |
| #6 | after_reset_action.png | 36.84 KB | manauwarsheikh |
| #3 | Core-Redirect.Reset_.To_.Front_.Page-2409657-1.patch | 548 bytes | stevenpatz |
| Screenshot.png | 32.03 KB | msg |
Comments
Comment #1
msg commentedComment #2
msg commentedComment #3
stevenpatzI've just set this to go to the front page, keeping the same message as before.
Comment #4
roya-rateshtari commentedI tested the patch and it worked as expected.
Comment #5
xjmThanks @MsG, @Roya-Rateshtari, and @StevenPatz, for the patch, review, and screenshots. I've always found this minorly annoying and confusing as well. I wondered if redirecting to the front page made sense, but I think it does. We don't want the user to end up back on the same form because that will confuse users as to whether the form has actually been submitted.
This issue was already tagged for a usability review, so setting back to NR for that signoff, but I think this is a good usability improvement.
Comment #6
manauwarsheikh commentedYes, I agree.
When a user request for "Reset Password" then the message should appear on the homepage "Further instructions have been sent to your email address." instead of showing login page again. And currently it is working for me.(attached screenshot)
Comment #7
manauwarsheikh commentedComment #8
manjit.singhComment #9
xjm@manauwarsheikh, thanks for testing! Per #5, a usability maintainer's signoff was requested for this issue (the "Needs usability review" issue tag was added to it at some point), which is why I set it to "Needs review." Restoring that status. :)
Comment #10
Bojhan commentedMakes sense, might need a re-test to see if this still works.
Comment #21
roderikIt still works. Now I hope this doesn't need a usability re-review after 5 years ;-)
(I do not know how stringent we are in requiring automated tests for everything; this change might not need a test to verify that we end up at the front page?)
Comment #22
quietone commentedOh, this is nice, I like this improvement. @roderik, thanks for giving this a nudge.
The patch does not apply to 9.2.x, so needs a reroll, adding tag. It look suitable for a novice, so adding tag.
The resolution in the Issue Summary does not match the patch, so the IS needs an update. This too is suitable for a novice.
Thx
Comment #23
quietone commentedI think it is safe to un-assign StevenPatz .
Comment #24
anushrikumari commentedComment #25
anushrikumari commentedRerolled patch #3 for 9.2.x
Comment #27
ressaThis is a great idea, and the patch applies and works fine, sending the user to the front page after requesting a password reset:
The test seems to fail though ...
Comment #28
ressaUpdating status.
Comment #29
roderikSorry for not being diligent; I just applied the patch manually to my local 9.2.x before testing, and it worked with a line difference of about 35. (And I thought tests which were still 'green', were running automatically every so often.)
The failing test (FunctionalJavascript\LayoutBuilderQuickEditTest) seemed like a fluke / unrelated to me; after having pressed the "retest" button on #25 it's now green. So this is tested.
Comment #30
roderikComment #31
roderikRelated issue which could be used (or closed as duplicate) if we want to backport to D7...
Comment #32
alexpottCommitted and pushed 5cb4fa9112 to 9.2.x and 61307db3bb to 9.1.x. Thanks!
Backported to 9.1.x as this is a usability improvement with little risk.
Comment #35
stevenpatzGlad to see this get in. Not sure why it was 'safe' to remove me. But anyway, it's merged.
Comment #36
quietone commented@StevenPatz, apologies, I didn't explain that. I meant that since you haven't work on this issue since May 2015, it seemed OK to unassign you.