I really like the way SwiftMailer integrates with Symfony. My sfDoctrineApplyPlugin uses it for confirmation emails.
My own feeling is that separate actions for emails are a pain because in the action that wants to send the email in the first place you usually have all of the necessary data ready to hand, and you really don't want to muck about with passing all of that data through to another action... then validating it again needlessly. Ugh. I never liked that in Symfony 1.0. Using templates for email is a win of course, but $this->getPartial allows us to do that. You might check out modules/sfApply/lib/BasesfApplyActions.class.php in sfDoctrineApplyPlugin for ideas. And for the getMailer() method, which takes care of a lot of common tasks relating to configuring the swift mailer object. -- Tom Boutell P'unk Avenue 215 755 1330 punkave.com window.punkave.com --~--~---------~--~----~------------~-------~--~----~ 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 symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
