[MAGNOLIA-3879] Add customizable validation message to controls Created: 10/Nov/11 Updated: 05/Nov/15 Resolved: 05/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface |
| Affects Version/s: | 4.4.2, 4.4.3, 4.4.4, 4.4.5 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Richard Unger | Assignee: | Philipp Bärfuss |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | control, dialogs, validation | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Date of First Response: |
| Description |
|
The "default" validation message is too general to be helpful for editors. Especially when the validation involves things like a 25 character limit, the message should really point out what is wrong ("Your input is too long. Please use a maximum of 25 characters."). We use the field description to inform the user about the expected format, but people still make mistakes, and are then confused by the generic validation message. This is particularly important when setting validationPattern on a ckEditor field. Since the (invalid) field contents are echoed in the message, and ckEditor fields typically have long content (and in HTML), the standard validationMessage does not fit in the javascript dialog, and is completely incomprehensible to the end user. It would be a nice (and easy to add) feature to allow customizing of the validation message, to complement the validationPattern setting. Solution: add a "validationMessage" property to controls (info.magnolia.cms.gui.dialog.DialogControlImpl). If the validation fails for the validationPattern, the control would then show the supplied validationMessage in the alert. |
| Comments |
| Comment by Magnolia International [ 10/Nov/11 ] |
|
Sounds reasonable. The team is hard working on 4.5 non-ui features, then will switch to new UI for 5.0, though... any chance you'd have a patch to do this ? That'd surely help integrating the fix faster ! |
| Comment by Michael Mühlebach [ 05/Nov/15 ] |
|
Given that the module this issue belongs to is no longer under active development, we're not going to address this issue any more. Instead we will focus on issues in all the other active modules. |