elod/li3_mailer

A plugin for sending email messages from your li3 application.

Li3 mailer plugin

A plugin for sending email messages from your li3 application.

Installation

Install and register the plugin as described by the manual.

Documentation

The documentation was created with the li3_docs plugin in mind, please see the readme.wiki for details.

TODO

• better documentation
• restructure View/Renderer/etc. (in lithium core) to better support inheritance (and support the Simple renderer/loader)

Credits

Thanks to nateabele, daschl, masom and the lively li3 community.

Copyright

See LICENSE.txt for details.

li3_mailer's Issues

$t-variable in templates not working

Hey guys,

Can you add support for g11n in templates? I would love to see this feature :)

Jeffrey

HTML escaping should be disabled for text templates

Right now, when you use normal template output syntax (i.e. <?=$foo; ?>) inside text templates, content is still HTML-escaped, which causes it to show up HTML-escaped in the resulting emails. The mail renderer should fix this by replacing $h in non-HTML templates with a pass-through function that directly echoes passed content.

Setting the subject from inside a template

It'd be really great if we'd able to set the mail's subject from inside the template similar to what $this->title() does for regular templates. That would allow us to have all the wording inside the template.

Embed Images Outside of Template?

@eLod - Is there any way to embed images without using the Html helper? So far I see that embedded images can be added directly when invoking li3_mailer\net\mail\Message. But how can I embed an image using Mailer::deliver(). This is assuming of course that cid is already in place via the html.

Generating absolute URLs

While this isn't a specific issue to li3_mailer, this lib could bring a first solution.

When dealing with emails, one would generate absolute URLs and avoid using relative ones URLs.
Calling Router::match() with an 'absolute' => true option do it, but sending emails from a li3 command break request environment and especially, the base host.

li3_mailer could expose a way to set the default host that will be used in all mailers.

PS: I ended up with doing a Environment::set('production' => $config)during the app bootstrap process