Thanks Tom. You're right, of course, about needing server-side validation. I don't want to *only* validate server-side, because I want to at least prevent accidental form submission with empty fields on submit. I guess I can't do that without displaying the asterisk, though. It's not as much of an issue with flash forms, anyway, since they don't submit when the user hits Return like regular forms do. Still, it would be nice to be able to omit the asterisks -- they're overkill on a simple login form. Thanks again for your answer.
Main Topics
Browse All Topics
by: tmcneerPosted on 2006-03-11 at 07:36:03ID: 16163207
You see to be mixing two issues here: first, as far as I know, there's no way to suppress the asterisk. There might be, somewhere deep in the Flex code (which is what is actually generating the Flash), but it seems doubtful, since the asterisk is a normal convention for denoting required fields.
But then you say, "I don't want to validate server-side" -- which doesn't have anything to do with the asterisk. The "required" attribute has nothing to do with where the validation takes place. You set where validation is done using the "validateAt" attribute. In Flash forms, "onBlur" and "onSubmit" amount to the same thing. You can use multiple methods by comma-delimiting them. So if you want validation done both on the client and server sides, you'd write 'validateAt="onBlur, onServer"'
If you don't want it validated on the server side, just leave that part out.
That said, it's never, ever a good thing to omit server-side validation -- although <cfform>'s server-side validation is not very robust. But it's better than none at all.
Tom