Issues
- wcm.io validation does not allow multiple validators to be attached to a single fieldWWCM-19Resolved issue: WWCM-19Stefan Seifert
- Clientlibs UI Extension | JS and CSS scripts are included multiple timesWWCM-18Resolved issue: WWCM-18Stefan Seifert
- Pathfield UI Granite validationWWCM-17Resolved issue: WWCM-17
- GraniteUI Checkbox does not set false when uncheckedWWCM-16Resolved issue: WWCM-16
- Clientlibs UI Extensions | Incompatible with ACS Versioned ClientlibsWWCM-14Resolved issue: WWCM-14
- Predicate for pathfieldWWCM-11Resolved issue: WWCM-11Stefan Seifert
- "value" - config property not used in numberfield if jcr:created and jcr:lastModifed is missingWWCM-10Resolved issue: WWCM-10
- configScopePathBrowser without a resourceWWCM-8Resolved issue: WWCM-8
- Basic Granite UI Extension to support array format for a multiple selection fieldWWCM-5Resolved issue: WWCM-5
- Basic Granite UI Extensions and Support for Dynamic Granite UI componentsWWCM-4Resolved issue: WWCM-4
10 of 10
We noticed that the selectors for the wcm.io validators are too restrictive, they require an exact match. The issue is that, when using multiple validators (it is actually possible to configure the
validation
-property as a string array property), the exact attribute matching will not work, causing the validator not to be triggered.In case of a string array property with multiple entries, the values are concatenated with a space (i.e.
wcm.io.pattern my.custom.one
).An easy fix would be to replace the
=
with~=
as is also done in other (OOTB) AEM validators.