[4.0] Displaying password minimum requirements in frontend registration#30456
[4.0] Displaying password minimum requirements in frontend registration#30456infograf768 wants to merge 1 commit intojoomla:4.0-devfrom
Conversation
|
@Quy |
|
@Quy |
|
@brianteeman Also, if you look at the strings errors, they do use Digits and Characters |
|
@Magnytu2 Yes, because you have not changed password rules so they contain more requirements than the length. You can do that in com_users options on tab "Password Options". Please do so and check the result. Thanks in advance. |
|
Yes everything works, except with the @ which must not be a symbol ? But I am happy to discover this function which I did not know. |
|
Please mark your test OK on issues.joomla.org |
|
I have tested this item ✅ successfully on 03d1366 This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/30456. |
|
Would this be better without having to add the rule attribute and tooltip and fix the duplication? Add to registration.xml: Change: Add: |
|
@infograf768 Great that you want to change both sets of strings to match I would prefer the much simpler "numbers" to either "digits" or "integers" |
|
@zero-24 Will come back after tests. |
|
I'm not sure whether that was for me but to answer your question when you can not get a value from the Database just fallback to the default values ;-) My proposal would be to show all of that next the message that the PW does not meet the requirements. As all that info should be in JS anyway but that is beyond my knowledge of JS at that point :-D |
|
But by Default it is only the 12 chars so the installer should be fine as it is and should only get the 'do not show the requiremets' xml switch so we do not dublicate that info. |
Not sure, digit is a single number. Number may be composed of one or multiple digits. |
I guess so but I also have to modify its description string, i.e. use the value of As I said, will first make a test and close this PR and create a new one. |
In English it is perfectly normal and expected to refer to numbers and letters in this use case |
|
Oxford Dictionnary I will stick to it. |
|
A dictionary and real world usage are very different. But as you always think you know better about a language that is not your native language just see what everyone else does. Feel free to write what you want in the french translation but in this use case the correct english is "numbers" |
|
In your list there are almost as many numbers of examples using https://community.ui.com/questions/airControl-2-Password-Requirements/068eeb2e-6c6d-49b6-b7a2-81f9d61a9a34 |
|
So you found three bad examples to prove your incorrect point. If google, facebook and twitter all use numbers thats good enough proof for me |
|
Closed in favor of #30473 to implement description tip instead of tooltip. |





Following #30437
Summary of Changes
Added a tooltip displaying the password minimum Requirements when registering in frontend
The new xml element is
rules="true"As I was at it I modified the tooltip display in Cassiopea as the default bootstrap white letters on black background was really ugly
This aspect can be modified by the people working on Cassiopea (if they prefer something else.)
Testing Instructions
Patch. Run npm ci
Define Password requirements in Users Options=>Tab Password Options
Actual result BEFORE applying this Pull Request
The password field does not indicate any requirements, forcing the new user to enter stuff and then modify depending on the Errors messages.
Expected result AFTER applying this Pull Request
or if different requirements
Note
If this accepted, we can implement in other core places.
Documentation Changes Required