Character Validation on Custom Fields

[kocourek]

We have a couple of instances where it would be beneficial to have a custom field type be limited to only numeric input. We currently use the standard text field, but inevitably someone enters alphabetic characters into the field. The non-numeric characters then break website features such as a filter slider. We have a process to QC these fields, but having the character validation built into the field would alleviate the headache.

To spread the use case a bit more, custom (Regex) / predefined custom field value validation would be a great enhancement. (email, numeric, telephone, range, datetime, color)

[Bruce - PhosphorMedia]

If its super critical, you could create a "Front Side" interface for product updates and use standard jQuery/JS validation routines.

[kocourek]

Thanks for the input Bruce. I agree that a client facing interface with standard validation routines would be a solution. The main point in posting as a dream feature is, well, it's a dream feature for us. But also to test the waters to see if custom field validation would be beneficial for others.

[Bruce - PhosphorMedia]

The main point in posting as a dream feature is, well, it's a dream feature for us. But also to test the waters to see if custom field validation would be beneficial for others.

Understand. Just wanted to give you an option instead of a "dream" :) (We've done several 'front side' admins for clients...many are surprised how easy and effective it can be because you can streamline the interface just they way you want. For some, its too limit access to fields, for others its to allow for 'outside' resources to do your work for you. For example, a distributor can add update products that they provide.