Somewhat important security issue: Import form removes validation rules

[Digo]

That wouldn't really help with the issue reported at it's core, because as mentioned previously, there are times when you just won't want a validator added on the front end.

See:

A date from the Date Picker is an invalid date!

Hi , I have a text input box with a date picker, I have set the format to DD-MMM-YY. [image] I also have set Date Validation on the same text input box. On the page the date picker works well, but the date validation does not recognize the picked date as valid. [image] Note: if I set the format to YYYY-MM-DD in the date picker, the validation sees the picked date as valid, but this format is considered not the best for user friendliness. I have tried a few experiments DD/MM/YY also does no…

A date from the Date Picker is an invalid date!

The validator expects a date in yyyy-mm-dd or yyyy/mm/dd format. You can just remove the validation from the front end (from the input) and only add it to the backend (in your server action) as the input always sends the date in yyyy-mm-dd hh:mm:ss to the server action no matter what the date format is set to. The date format option of the date picker component is only for displaying date to the users.

The simple solution for this issue is to only add the validator on the server connect side, which works perfectly as you'd expect. But if you then reimport the form, that validator will disappear, letting someone post any kind of data since it won't be validated.

(again, you could get around that by adding it in as a validator step, but as I mentioned earlier, it's not intuitive for new users nor should it really be needed when you can just add it under the inputs)