tagErrorMsg definitions
>> >> aren't spitting out their messages.
>>
>> >> I did a search, and found it on line 1685 of model.php What I did, is
>> >> changed 'This field cannot be left blank' to '1'. It
ut my tagErrorMsg definitions
>> >> aren't spitting out their messages.
>>
>> >> I did a search, and found it on line 1685 of model.php What I did, is
>> >> changed 'This field cannot be left blank' to '1'.
allowEmpty actually translates to 'not set' i.e. if the field is not
set in the model then don't fail validation. I think what you're
looking for is similar to me - i.e. 'allowBlank' - ala
https://trac.cakephp.org/ticket/2092 Use at your own risk as this
patch may not be accepted and 1.2 is stil
That's pretty much all accurate. Form validation is still somewhat of
a work-in-progress in 1.2, and displaying errors will be handled by
FormHelper::error() once the implementation is finished (it is already
used in FormHelper::input()), at which time HtmlHelper::tagErrorMsg()
will be deprecated
1685 of model.php What I did, is
>> changed 'This field cannot be left blank' to '1'. It works now, but
>> I'm thinking maybe tagErrorMsg is used differently now.
>>
>> Here is an example of how I've been using
The way it appears to work now (I'm sure nate will correct me if I'm
wrong) is to put your error messages in the model. Here is an example
of an email validation:
var $validate = array(
'email_address' => array( array('allowEmpty' => false
,'message' => 'Invalid email add
Hello, in the latest 1.2 SVN, I can't get validation to work. Well,
it is working, the empty fields are being flagged as they should be
for not meeting cake's regex constants, but my tagErrorMsg definitions
aren't spitting out their messages.
I did a search, and found it on line 1685 of model.p
