I'd like to hear some suggestions on cakeifying an existing system.

Cake's validation is wonderful, but it only allows "yes this is good"
and "no it isn't". I've got an application I need to port that has
automated warnings built in for some fields.

Although my system is quite specific (it's a historic family tree, so
most of the warnings are like "Warning: this marriage is between two
cousins / brother and sister, are you sure?), I could see a generic
application, for example for URLs (warning: this URL returns a 404,
are you sure you want to add it?) or passwords (this is a crappy
password choice, use it at your own risk...).

My old system gave each warning generated a session-level id and
presented an appropriate checkbox in the field 'error' position. The
validation routine checked if the checkbox was checked for each
registered warning and ignored it if appropriate. If there were no
errors, and no unchecked warnings, the form went through.

My old system was not very flexible, a mish-mash of php includes and
whatnot, and I need to cakeify it.

So, any suggestions on how to introduce this functionality to cake,
without rewriting the form helper or model validations? I've got a few
ideas but I'd like to hear input.

(Once I've got a solid "normal" foundation for it, I'd like to extend
to js/ajax too, but this is definitely for later)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to