Standardising Transactional Email Templates

Tony Feltham asked on November 17, 2016 18:13

I am trying to set up email header and footer block to standardise transactional emails.

I have tried creating an email template(EmailHeader and EmailFooter) and then including it in another email template and I have also tried creating a transformation and then Applying the transformationfrom within an email template. In both cases nothing gets pulled through.

Below shows the content of both Email Templates

Please can you point me in the right direction. Many Thanks Tony

OPTION ONE – Including another Email template using its Code Name

{#EmailHeader|(encode)false#}

Thank you for registering on the our website.

Your user name for the site is {%TrimSitePrefix(username)%}

A registration email has been sent to our site administrators and the will contact you shortly regarding full access to the site and all its resources.

In the meantime please login and start you first Project list

Many Thanks

{#EmailFooter|(encode)false#}

OPTION TWO – Applying a transformation that includes the required HTML

{% ApplyTransformation("CMS.Root.EmailHeader") #%}

Thank you for registering on the our website.

Your user name for the site is {%TrimSitePrefix(username)%}

A registration email has been sent to our site administrators and the will contact you shortly regarding full access to the site and all its resources.

In the meantime please login and start you first Project list

Many Thanks

{% ApplyTransformation("CMS.Root.EmailFooter") #%}

Recent Answers


Trevor Fayas answered on November 18, 2016 00:23

Another way of doing this, as much as it's not necessarily what it's meant for, is to make a Localization string "custom.EmailHeader" and "custom.EmailFooter" and in your email template, use {$ custom.EmailHeader $} and {$ custom.EmailFooter $} to pull in that content.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.