Georg, I actually think that your use of the plugin is far from its original purpose. The plugin does versioning, you want to do workflow. So no, the plugin is not very well designed for your use, but I guess it will probably stay that way...
Cheers, François 2008/3/28, Georg Sorst <[EMAIL PROTECTED]>: > > > Hey list, > > I am currently looking for a way to create a new resource version > without modifying the resource itself. The problem is that in order to > create a new resource version the behavior's preSave() and postSave() > hooks have to be called which is done implicitly by calling the > resource's save() method. If I do this the resource will be modified > obviously. The conditional versioning doesn't help either as this does > the opposite of what I want (modifying the resource without creating a > new resource version). > > What I'm currently doing is manually calling preSave(), addVersion() and > postSave() along with some other minor tweaks. This works but requires > quite some redundant code. So, am I missing something or is such a > functionality not included yet? > > The background is that I want to (ab)use > sfPropelVersionableBehaviorPlugin for some sort of approvable- changes- > system. This means for example when a non-admin user edits an object the > object itself is not modified but a new version is created > nevertheless. The admin can then review this change and either approve > and merge it with the object or reject it and just discard the resource > version. > > Thanks and cheers, > Georg > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
