Hey Stephen,
while there's nothing wrong with creating a plugin, even to just share
one template, for emails I prefer to wrap them in classes.
As Gustavo says, it sucks a bit if there's complex HTML involved, and
I'm currently looking at integrating the templating standalone
component to be able t
If it's just a text email, you could encapsulate the message in a message
object so you don't have to use the template. But, as I said, this would be
just for a text email, With HTML it would be a little cumbersome.
On Mon, Aug 2, 2010 at 12:11 PM, Stephen Melrose wrote:
> I thought of that, but
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 wrote:
> You should use a plugin, put your templates in the same module and
> enable the plugin for all the
> applications
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 wrote:
> Hey,
>
> I've just been reading up on email best practices for 1.3/1.4.
>
> It all makes sense, however my project h
