-
- 249 Posts
Have you tried:
[[+int01:notempty=`INT 01 Selected<br/>`]]
[[+int02:notempty=`INT 02 Selected<br/>`]]
or..
[[!+int01:notempty=`INT 01 Selected<br/>`]]
[[!+int02:notempty=`INT 02 Selected<br/>`]]
lo9on.com
MODx Evolution/Revolution | Remote Desktop Training | Development
-
- 236 Posts
I’ve been off this for a while but your post works cyclissmo, many thanks!
-
- 249 Posts
You can always just remove the [tt]:required[/tt] validator from the email field, but that will allow empty emails to pass. I don’t think you want that.
AFAIK the proper way to approach this is to create a snippet to validate the email according to your criteria, and then register it as a custom validator.
The only other alternative that I can think of is commenting out the first statement in the [tt]email()[/tt] method in [tt]fivalidator.class.php[/tt]. That should stop empty emails from passing through the [tt]:email[/tt] validator. Only problems is, that change will ’undo’ when you update the package.
lo9on.com
MODx Evolution/Revolution | Remote Desktop Training | Development
-
- 236 Posts
Thanks again cyclissmo, yeah I briefly looked at using a custom validator. I guess the snippet would contain some kind of regex to validate the email. I did have a look at the fivalidator.class.php to see if I could use the code from there but it seems like a lot of work for a small non critical feature. Maybe when I get some time I can take a look.
Thanks for the help.