Page History

Blesta 3.0 uses the H2o Template system for parsing Email Templates. The following is an overview of its basic usage. We've overridden the default {{ var_name }} with { var_name } for simplicity, but that's the only way in which the following documentation differ from any official H2o documentation.

Conditional Statements

{% if id > 3 %}

This will print out if $id is > 3

{% endif %}

Loops

{% for user in users %}

Name: {user.first_name} {user.last_name}

{% endfor %}

Assuming:

$users = array(
    array(
         'first_name'=>"First name",
         'last_name'=>"Last name"
    ),
    array(
         'first_name'=>"First name 2",
         'last_name'=>"Last name 2"
    )
);

Loops can also take advantage of limits:

{% for user in users limit:1 %}

The above would only cycle through the loop one time.

Filters

Filters are applied to individual variables and are preceded by a pipe symbol (|). Parameters are passed to filters using a comma (,) separated list.

{past_due | set_default "Not past due"} // Produces "Not past due" if past_due is false

Multiple filters can be applied in succession:

{past_due | set_default "not past due" | capitalize} // Produces NOT PAST DUE if past_due is false

Supported Filters

{"1.2345" | currency_format "USD"}

{invoice.total | currency_format invoice.currency}

{"some string" | md5}

{"some string" | sha1}

{"12345.6789" | numberformat 2, ".", ","}

 {"some string" | wordwrap 5, "\n<br />"}

{" some string " | trim}

 {"some string" | upper}

 {"SOME STRING" | lower}

 {array_of_items | first}

{array_of_items | last} 

 {array_of_items | join ', '}

 {array_of_items | length}

 {array_of_items | urlencode}

 {"some string" | hyphenize}

 {"http://domain.com/" | urlize}

 {not_set | set_default "default value"}

{"some date string" | date "Y M d"} eg.
{invoice.date_due | date "Y M d"}

Debugging

Adding the following tag to any email template will enable debugging, and display data key value pairs:

{% debug %}