User tests: Successful: Unsuccessful:
Pull Request for Issue #23345 .
Confirm Password field removed from user edit in backend
code review or test whether user edit forks as expected and Confirm Password is not present.
No Confirm Password field and user edit works.
Confirm Password field exists and user edit works
|Category||⇒||Administration com_users Language & Strings|
I see that the password is removed from the user edit view.
But there are about 30 places where the password2 is used in the code.
It is checked in the models and appears in different views and models in the frontend.
So I think it is too early for submitting a test result.
Why would you want to do this? For BC you should at least add it as a config option which is showing both by default.
The second password is only wasted time and no longer up to date in modern apps (my opinion).
I do not insist but why then do we have the new password with the "plain text" button?
If it is a B/C problem, we need a param and or a solution for the password2 check. But I do not see a big B/C problem. The password2 is not in the database. It could be used in extensions of the registration form, but I am sure that there we can find a solution.
|Category||Administration com_users Language & Strings||⇒||Administration com_admin com_users Language & Strings Front End Libraries|
should at least add it as a config option
Please NO more switches...
|Category||Administration com_users Language & Strings com_admin Front End Libraries||⇒||Administration com_admin com_users Front End Libraries|
@tonypartridge the password shouldn't be visible by default and also in the field (password) was added a button to reveal the text just for this scenario. FWIW the field still needs to become a custom element, there used to be a PR by me and would be really nice if someone resurrects it because the current code is not production-ready...