kim_purcell
Kilo Explorer
div warrior.jpgIf your email client template is not working after upgrading to Eureka P5 or later, this may be because you have sneaky <div> tags infiltrating your script.

So instead of this script:
<mail_script>
&#8232;template.print("I'm an instant star. Just add water and stir. — Bowie"); &#8232;  

</mail_script>

You'll get this script: <div><mail_script></div><div>template.print("I'm an instant star. Just add water and stir. — Bowie");</div><div></mail_script></div>

When the system formats the text in the templates, <div> tags like to invade to indicate separate lines. The <div> tags also appear in your script if it extends more than one line. These tags invalidate the script, which prevent it from running. However, the script will work if you move the contents of the script to the Notification Email Scripts and use the script in the template body.

To move the email template script to the Notification Email Scripts:

  1. Navigate to System Policy > Notification Email Scripts.
  2. Create and name the new script. For example, BOWIE.
  3. Navigate to System Policy > Email > Client Templates.
  4. Create or edit a template.
  5. In the Body field, enter ${mail_script:BOWIE.
  6. Click Submit.

You should now be able to view the text in your email template:

BlogScript.png

For more information, see Email client templates that use mail scripts do not work after upgrading to Eureka Patch 5 or later.

1 Comment