Make WordPress Core

Opened 13 years ago

Closed 7 years ago

#16318 closed enhancement (duplicate)

The reset password process could be clarified

Reported by: paolal's profile paolal Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.1
Component: Users Keywords: needs-patch
Focuses: ui Cc:


I find the process of resetting a user password confusing, and sI guess I am not the only one.

Here is why:

The fist screen in this process is almost ok:

only the text on the button is confusing as users won’t “get a new password” but are going to input a new password (I guess this is an heritage of the past procedure).

The second screen is where most users get lost:

I think that the login form should not be visible here as it gets the user’s focus, so they do not see the text above telling them to check their mailbox and do not know what to type here.

I know that changes are planned in the reset password process, but these two relatively small changes could make the process a lot easier to follow for users.

Attachments (2)

16318.diff (1.8 KB) - added by stephdau 13 years ago.
Patch to implement Automattic Happiness Engineers suggestion
16318-alt.diff (2.7 KB) - added by stephdau 13 years ago.

Download all attachments as: .zip

Change History (13)

13 years ago

Patch to implement Automattic Happiness Engineers suggestion

#1 @stephdau
13 years ago

Closed dupe: #16319

#2 @nacin
13 years ago

  • Keywords ux-feedback added

Some of the code you added (to suppress the login form) was removed in r12981, due to the concerns in #11141. But most of that no longer applies due to the changes in #5919. I will have to go through the program flow again, but what you describe and suggest makes sense.

Additionally, 'Get New Password' was from pre-#5919 -- I found the string in the same spot in 3.0, when we sent a reset password to their email address.

Marking for ux-feedback and sending this to Jane. I am wondering if there is a way we can at all do any improvements without changing any strings. That said, we've yet to kick over a single string change to the translators, and we're a week out (with a weekend) from launching anyway.

Also, s/Login/Log in/, or you're feel the grammatically pedantic wrath of Mark (me too). :)

#3 @nacin
13 years ago

  • Milestone changed from Awaiting Review to 3.1

I'm putting this into 3.1 for a review for now. Going to check it out in a bit.

#4 @stephdau
13 years ago

@nacin: indeed. String translation is one of the reasons I wanted this done from core up instead of as a patch on Thanks for looking into it. :)

Nikolay also suggested that showing the login form when showing the "you password has been reset" notice would make sense. On the other hand, this is handled in another case, and would require a switch from "aborting" the case with login_footer() to using a redirect.

I'm submitting an alternate patch here, same as 16318.diff, with redirect handling.

13 years ago

#5 @nacin
13 years ago

Reminds me of the importance of #15384.

The login form needs to be shown when you see 'Your password has been reset.', so they can log in. Per the comment from #5919 I pointed out in #15384, I would have liked the user to be logged in at that point.

#6 @stephdau
13 years ago

I would have liked the user to be logged in at that point

Even better indeed.

#7 @jane
13 years ago

  • Component changed from General to UI
  • Keywords 3.2-early added; ux-feedback removed
  • Milestone changed from 3.1 to Future Release

Not for 3.1.

#8 @nacin
13 years ago

  • Owner login, reset password deleted
  • Status changed from new to assigned

#9 @sabreuse
11 years ago

  • Component changed from UI to Users
  • Keywords ui-focus added

#10 @chriscct7
9 years ago

  • Keywords needs-patch added; 3.2-early removed

#11 @DrewAPicture
7 years ago

  • Milestone Future Release deleted
  • Resolution set to duplicate
  • Status changed from assigned to closed

Let's centralize discussion over on #36010.

Note: See TracTickets for help on using tickets.