I thought of that, but it just seems like the wrong approach, as the
templates aren't really a plugin.

Is that really the best approach?


On 2 August 2010 15:51, pghoratiu <pghora...@gmail.com> wrote:

> You should use a plugin, put your templates in the same module and
> enable the plugin for all the
> applications that need it.
>
>    gabriel
>
> On Aug 2, 5:26 pm, Stephen Melrose <step...@sekka.co.uk> wrote:
> > Hey,
> >
> > I've just been reading up on email best practices for 1.3/1.4.
> >
> > It all makes sense, however my project has two applications (frontend
> > and backend) and both will be sending the same email.
> >
> > I don't want to duplicate my template into both applications, but at
> > the same time I don't know how to call it globally outside of an
> > application.
> >
> > Can you make a module global to multiple/all applications? Is that the
> > best approach?
> >
> > Steve
>
> --
> If you want to report a vulnerability issue on symfony, please send it to
> security at symfony-project.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<symfony-users%2bunsubscr...@googlegroups.com>
> For more options, visit this group at
> http://groups.google.com/group/symfony-users?hl=en
>

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.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

Reply via email to