On Dec 28, 5:01 pm, ProFire <[EMAIL PROTECTED]> wrote:
> Yup!!!
> I believe that's a very good way to validate existing fields and
> output errors for it.
>
> What about the non-existing fields?
>
> Example:
> Password: <input>abc
> Verify Password: <input>abc
>
> Personally, I would feel that a notice like "account/verify_password
> was not inserted because field don't exist in table `account`" would
> be very very useful.
I think that would very quickly get annoying. you can add validation
rules for virtual fields, and if the cause is a misspelling, when you
debug you'd spot that ;). I don't see the benefit in adding logic
which would always be executed to cater for a development only
problem.
> Anybody have a way to output such messages automatically?
If you want that, use beforeValidate to add an error message for
everything in $this->data that isn't what you are expecting.
hth,
AD
PS. Emphasis on the "debug".
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
