Yeah. I've gotten used to it being separate and now prefer it in case I ever have the need to not run something like beforeSave(). Although I've never needed it to be separate, I'm sure it can be said that there is a scenario where it might be needed.
-- Jeff Coughlin On Feb 10, 2014, at 9:21 PM, Justin Carter <justin.w.car...@gmail.com> wrote: > Nope, I think the only time Core runs beforeSave() is when a form (or wizard) > is processed, and in createFromUpload() (for file/image formtools) - it > doesn't get run within createData() or setData(). I'm not entirely happy with > the way that part of the API currently works, but it's easy enough to call > beforeSave() manually before create/setData(). > > cheers, > Justin > > -- > Justin Carter > http://www.madfellas.com/blog > http://twitter.com/justincarter -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: farcry-dev@googlegroups.com To unsubscribe, email: farcry-dev+unsubscr...@googlegroups.com For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry --- You received this message because you are subscribed to the Google Groups "farcry-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to farcry-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
