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 (that 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 a 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 process the checkout and click throug admin panel to send yourself emails.
this one might help you:
As a part of my vt-devutils modules collection, dev-mails offers you a preview function for some major 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.
here is what you will get:
The first row on the blue toolbar shows you emails you can preview, the second row will show you the email subject and a button for reloading the preview. The (?) button is currently not working
below the toolbar you see the preview for the html mail on the left sind and the plain text mail on the right side. The HTML mail is rendered in a iframe, so OXID admin css will not affect it.
how ot works:
order user and order owner mails
at first, you need to sign in your shop frontend and put some stuff into 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.
“order has been sent” mail
you need at least one finished order in your account, to preview this email.
getting raw HTML
on top of the preview function you can get the HTML code of the emails, e.g. to run it through inliner or for litmus tests.
you will find generated html files inside logs directory of 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”.
the basic workflow:
- develop your mail tempaltes and preview within the browser
- get the email’s html code from generated files
- send a testmail, e.g. with Litmus PutsMailor 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/