You *could* call mail(). Configuring PHP's mail() correctly isn't an outrageous requirement IMHO. That doesn't give you the benefits of the old system re: use of templates, slots, components etc. though. Is there perhaps a new and fairly painless 1.1 way to generate a request to another action and get the response as a string? That would go really well with a call to mail().
If mail() isn't a good answer, then perhaps you should write a new sfEmailTemplatePlugin that provides good services, make it available to everyone, and make your other plugins dependent on it (via package.xml) so that installers know it is needed. I have releases plugins dependent on other plugins, the installer does correctly flag what the user needs to install first. On Tue, Sep 2, 2008 at 3:57 PM, gimler <[EMAIL PROTECTED]> wrote: > > Hello, > > i started to port the forgot password and register function from 1.0 > version of sfDoctrineGuardPlugin to 1.1 version. > > so now i will send an email but there is no mail support in symfony > 1.1. > so is there a workaround/guideline to send mails in plugins? > > so i think all plugins should use a static user function to send mails > so that we don't must implement for each plugin a new way to send > mails ;( > > What do you think? > > > greetings > gimler > > > -- Tom Boutell www.punkave.com www.boutell.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
