Thanks, but the update vs.create distinction is not the problem here. We always want a country mandatory, whether the user is registering (ie. creating a new record), or changing his profile (ie. updating).
But we don't need a country when the user logs in, or when the user requests a password change. All these forms: registration, updateProfile, login, changePassword, forgotPassword are validated against the user model. But the validation rules have to be different for each form. Perhaps a stronger example is the password: it is mandatory on the registration form, the login form, and the changePassword form; but, is not required on the forgotPassword form, or the updateProfile form. It makes sense to have the data "type" and "values" be defined at the model level, since these are characteristics of the data. However, whether the field is mandatory or not, that is often more a characteristic of the form than the data. Any ideas? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
