[MGNLFORM-17] Validation possibilities are wrong when adding a new field Created: 02/Apr/09  Updated: 27/Nov/13  Resolved: 25/May/09

Status: Closed
Project: Magnolia Form Module
Component/s: None
Affects Version/s: 1.0.1
Fix Version/s: 1.0.1

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Teresa Miyar
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLFORM-18 CLONE -Validation possibilities are w... Closed
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   

The current values for "Validation" in the dialog are

  • none
  • no (sic) a valid number
  • not a valid email address

These are (I suppose) the error messages displayed to the end user when a form wasn't filled-in as expected.
These values/labels should instead be:

  • None
  • Must be a number
  • Must be a valid email address


 Comments   
Comment by Christoph Meier [ 27/Nov/13 ]

it's fixed and very old.

Generated at Mon Feb 12 05:36:02 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.