I tried to use the other revision behavior, my biggest complaint is
the requirement for an additional shadow table for each model you want
to backup. Also I tried to get it to work for a while and it seemed
broken. The last version I had seen was in the bakery, I just noticed
that it had been upd
>From a glance I see only 2 code flaws:
"private" declarations shouldnt be used inside a framework without
very good reason to do so (use "protected" instead)
->Save should probably be ->save
and it would probably be a good idea to make a test case for it.
especially since revisions and everything
I like the principle, but how does it work in practice? A few questions:
- I haven't looked at the code, but my guess is that you are storing an array?
- You also mention that it stores related data. So does this mean that if a
table can be updated from two places - one with a save and the other
Not sure if anyone else has been looking for this like me, but I
created an easy to use simple versionable behavior for cakephp 1.3 it
hooks into the beforeSave callback and grabs a copy of the data before
it changes and stores it in a revsions table. The great thing about
this plugin is that you
