Bug #22870 See Comments

Language around changing member password misleading

Version: 3.4.7 Reporter: Derek Hogue

When changing another member’s password, the final input is labelled “Current Password.” Although the instruction text reads “You must enter your password to save,” the first time any client of mine goes to change another member’s email or password they email me asking me to do it because they “need the member’s current password to change it.”

Clearly this was designed with the member changing their own email or password in the CP - but it breaks down when an admin is doing this (which in my experience is almost always the case - most self-updates are done via a front-end form in my work).

It would be great to change the label for this input to “Enter Your Password” when the member changing the profile is someone other than the subject member.

  • Hi Derek,

    Thanks for the report, I can see how in the context of that form it would be confusing. It wasn’t designed to be from the point of view of the member being edited, but of the person filling the form. The “Current Password” field is for double authentication in certain forms in the CP. Email settings and other forms have this same field. The field is visually tied to the submission controls. It also has the instructions “You must enter your password to save.” further explaining what the content of that field should be.

    I will look into it being more contextually aware, but I consider this a feature request and not really a bug.

    James Mathias
    05th January, 2017 at 12:25pm
  • Gotcha, I know it as pushing it to call this a bug. But I will reiterate than from the real-world experience of over a dozen different clients now (no joke!), this field is always interpreted on that page to mean “the member’s current password” -not “the logged-in user’s password.”

    Derek Hogue
    05th January, 2017 at 3:46pm
  • Thanks Derek, I can see that. I’ll put in a request to change the language to make it more clear.

    James Mathias
    05th January, 2017 at 3:48pm

You must be signed in to comment on a bug report.

ExpressionEngine News

#eecms, #events, #releases