Hi, maybe I shouldn't have used the existing issue for my problem... But it seems to be about the same problem: the input filter extension processes an empty string as valid, but in a required form field this should not be the case.
The empty check is not about weather the field is set or not (this is handled by REQUIRED|OPTIONAL), but about weather it has a non empty value or not. Instead of "require_string" it is maybe better to call the filter "non_empty_string"? What I want to solve is: a) REQUIRED field (e.g. name) b) filter_type=string c) if user didn't write anything into the input it should be invalid (the string filter of the filter extension allows empty strings, therefore a check for the empty string is needed afterwards...) Hopefully it's clear now what I want and what most likely the author of the issue wanted, too. Regards Andi Derick Rethans schrieb: > On Fri, 9 May 2008, Derick Rethans wrote: > >> On Wed, 7 May 2008, Andreas Schamberger wrote: >> >>> #011394: UserInput::emptyValue >>> http://issues.ez.no/IssueView.php?Id=11394&activeItem=2 > > Just wondering about this one, why can't you just mark them as OPTIONAL > instead of REQUIRED? > > regards, > Derick > -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
