On Aug 2, 12:54 am, Scott Stroz <[EMAIL PROTECTED]> wrote: > Some more questions if you don't mind. > > 1. On one content type, we may need to do some manipulation of data > before being saved, where in your example would I include that logic?
Essentially the object is commited to the database in the closing tag of ft:processformobjects. So you can manipulate content before saving at that point. Steve points out the beforeSave() and afterSave() events -- but be aware these are *always* run -- so this might not be useful if you need to do specific manipulation for this edit handler. > 2. On several content types, we will need to execute some external > code after being saved, where in your example would I include that > logic? afterSave() would be a good choice. > I assume I can put this logic inside <ft:ProcessForm /> but not sure > where. I'm working on some ft:form, ft:object, etc examples based on a nascent farcry blog plugin. A comment object needs to utilise all of these features for spam blocking, emailing, and so on. Will try and step up the pace and get something out shortly. -- geoff http://www.daemon.com.au/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" 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/farcry-dev?hl=en -~----------~----~----~----~------~----~------~--~---
