Developing Email Templates for OXID eShop

Developing Email Templates for OXID eShop

Developing Templates for OXID eShop isn’t that easy if you are not familiar with all the smarty stuff and confusing folder structure for tempaltes (which changes every two years).

Designing email templates is even harder, because of differen clients and their bad old HTML rendering engines. There is lot of extra work to go throug checkout process to get the email in your inbox. And as a developer you should test your mails in several email clients and mail providers. Basically 90% of the time you buy some stupid stuff in your shop to send yourself emails and check the changes you did.

Developing Email Templates for OXID eShop
dev-mails offers you a preview function for most important emails of your shop including html and plain bodies.

In actual version of the module you can preview the following emails: reguistration, registration confirmation (for private sales), forgot password, order email for user, order email for owner, order has been shipped, double opt-in.

order user and order owner mails:

First, you need to sign in your shop frontend and add some stuff to your basket, but you don’t need to go through the checkout. Dev-mails will use your saved basket for the preview function. Unfortunately you can’t preview coupons this way, cause they aren’t saved in baskets. Payment and delivery methods are hardcoded, too. I will try to improve it in the near future.

“order has been sent” mail:

You need at least one finished order for your account, to preview this email.

getting raw HTML:

On top of the preview function you can get rendered HTML code of all emails, e.g. to run it through inliner or for litmus tests.
You will find generated html files inside logs directory in your shop. E.g. if your email subject is “Thank you for your order”, the code will be saved in “logs/thank-you-for-your-order.html”.

suggested workflow for email development:

  • develop your mail tempaltes preview within the browser
  • get the email’s html code from generated files
  • send a testmail, e.g. with Litmus PutsMail
  • or pass the HTML code through inliner ( inliner.cm or Ink inliner ) and run litmus tests.
  • if you have a gmail account, you also can use this for sending html mails: http://ctrlq.org/html-mail/

 

0.00 avg. rating (0% score) - 0 votes
0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *