Uploading a new Email Design System to Taxi can be a daunting moment. In this article, we'll explain what the most common error messages you might see mean, and share tips on how to fix them.

Google Fonts URL is using a wrong format

This means that you've referenced a Google Webfont using an incorrect file format. Google Fonts chooses which version of a font to serve depending upon which device is requesting it - this won't work in email clients.

To fix this, you'll need to get a direct link to the .woff2 version. This makes sure that all email clients that support custom fonts will then load the Google Font.

Learn how to get the .woff2 version of a Google Font

References to fields which do not exist

This warning usually occurs when the field name doesn't match what you're referencing, perhaps because of a slightly different naming convention or a typo. This warning is often paired with a 'Fields have been made which are not used anywhere' warning.

Fields have been made which are not used anywhere

This warning usually occurs when the field name doesn't match what you're referencing, perhaps because of a slightly different naming convention or a typo. This warning is often paired with a 'References to fields which do not exist' warning.

References to fields of the wrong type. 

This warning usually appears when the replace-href is being set from a field that doesn't contain type href. This means the link tracking manager will not be able to read it. You must ensure that href fields are always used to set hrefs. 

Liquid doesn't reference any variables in attr

Liquid doesn't reference any variables in attr

This warning means that the liquid used doesn't reference any variables in attr. This is valid, and will not stop you from uploading the Email Design System, however commonly this is a mistake and reference will need to be input.

#{e.name} name is not unique

A name used is not unique. This applies to modules, fields, editables etc. This warning will appear when, for example, you have 2 modules with the same name in a modulezone or you have two editables with the same name in an editable, and so on. In this case, each name should be unique and should not repeat.

<module> element found as a child of a <table> element

This warning means a <module> element has been found as a child of a <table> element. Only <tr> <td> <tbody> or <thead> elements are allowed as children of a <table> element.

rich.selection_text not used in rich-editable-style

You will see this warning when a rich editable style has not specified where the text goes. You must use {{rich.selection_text}} in a replace= attribute, to show where the highlighted text should go.

Liquid code found in #{attr_name} attribute where it will be ignored, perhaps you meant replace-#{attr_name}

Liquid code found in #{attr_name} attribute where it will be ignored, perhaps you meant replace-#{attr_name}". This warning typically appears when liquid code has been used within a href. This will not stop you being able to use the Email Design System, but there may be some fields that don't work as you'd expect if you have liquid code in a normal attribute.

Did this answer your question?