Hi Kamal,
default forms messages are internationalized, so you can change the
default message with something else acting on the i18n bundle files.
Simone
Kamal Bhatt wrote:
Simone Gianni wrote:
Hi Kamal,
remove the fd:regexp validation from non-string fields. You don't
need it.
Thanks. However, the fail message is appalling, how do I change the
error message to be something nicer?
Simone
Kamal Bhatt wrote:
What do I do with the class cast exception?
Simone Gianni wrote:
Hi Kamal,
AFAIK you cannot (and don't need) to apply a fd:regexp to an
integer, it should give you class cast exception. Validation is
applied after conversion takes place, and the convertor for an
integer will not allow presence of letters by itself.
Simone
Kamal Bhatt wrote:
OK, this is a mistake on my part. This is a problem not with
validation as I thought but with form in general (ie it is not
saving even when the fields are valid). I will probably repost
when I have looked into this further.
Cheers.
Kamal Bhatt wrote:
Hi
I have a cform with the following field:
<fd:field id="min_duration" required="false">
<fd:label>Min Duration</fd:label>
<fd:datatype base="integer"/>
<fd:validation>
<fd:regexp pattern="[0-9]*"/>
<fd:range min="1" max="99">
<fd:failmessage>Max duration must an integer greater
than 1 and less than 99</fd:failmessage>
</fd:range>
</fd:validation>
</fd:field>
When I enter a non-integer character (eg 'a'), the cform fails on
save. All other validation works, but obviously, validation does
not work until the field is bound to the variable. My question is
how to get the field to validate without using javascript (at the
form template level) to do so (for the sake of consistency).
Cheers.
Kamal.
--
Simone Gianni
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
