[MGNLUI-5685] Magnolia Validators Do Not Work If Configured Through JCR Created: 25/Feb/20  Updated: 30/Sep/21  Resolved: 30/Sep/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.1.3, 6.1.4
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Julian Nodarse Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: y2k
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: XML File config.modules.ui-admincentral.dialogs.editUserProfile.form.tabs.user.fields.pswd.validators.xml    
Issue Links:
Problem/Incident
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

info.magnolia.ui.form.validator.definition.EmailValidatorDefinition
and
info.magnolia.ui.form.validator.definition.RegexpValidatorDefinition do not validate correctly when configured through the JCR.

Both validators work fine on 6.1.2. The issue shows up with 6.1.3. and 6.1.4 (including the demo).

A workaround for this is to use decorations.

As an example you can test the attached validator. Create a new user with some password. Then log in to this user, try changing the password to comply with the validator and you will see that the error validation will appear incorrectly.
You can use test password: Notatest123!
Extra note: I’ve tested the regex and it is fine.



 Comments   
Comment by Marta Kobus [ 30/Sep/21 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

 

Thank you,

The Magnolia Team

Generated at Mon Feb 12 09:29:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.