Alexandru-Emil Lupu wrote: > Hi! > i have a question about the new sf 1.3 getMailer method ... i guess it > would be better to be inserted into sfComponents as sfActions extends > sfComponents. > > I do think that is not in the right place, because i have met a problem. > > 1) had several emails to send form different actions of my project, so i > have decided to move all the mail actions to a new module called Emails. > 2) I have created a new "component" and i have inserted there the code > that i had for emails, to be much easier to access from other modules by > using $this->getComponent() > 3) After a short while i have noticed that i need to pass a sfActions > instance to the component just to be sure that i have access to the > getMailer method ... > > maybe i have done something wrong by moving all the email actions into > the component, but it was the single way that i have seen at the moment > not to Repeat myself ...
If you have a lot of emails, create classes for them that extend Swift_Message. That way, it is then a matter of create the right message: $this->getMailer()->send(new ConfirmationMessage($user)); Fabien > > I dunno ... What is your opinion ? > > Alecs > > -- > As programmers create bigger & better idiot proof programs, so the > universe creates bigger & better idiots! > I am on web: http://www.alecslupu.ro/ > I am on twitter: http://twitter.com/alecslupu > I am on linkedIn: http://www.linkedin.com/in/alecslupu > Tel: (+4)0748.543.798 > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
