Correct Email Template validation bug: variables used above meta definitions

Correct Email Template validation bug: variables used above meta definitions

Straightforward bug: let's say you wanted to add a global variable to the top of your email template. For example, if someone knows they need to send emails in multiple languages from one template, they should define the language correctly for screen readers, right? So, you'd have something like

<!DOCTYPE html>
<html xmlns="https://www.w3.org/1999/xhtml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" lang="${lang}" xml:lang="${lang}">

[...]

<meta class="mktoString" id="lang" mktoname="Email Language" default="en">
‍‍‍‍‍‍

Nothing groundbreaking here, just adding the ability to swap language if needed. However, the UI will indicate that the ${lang} variable is not defined when viewed. When running validation, this issue will not be flagged, and indeed you can use it without issue, but having the error pop up can be concerning to those who are not already aware of the setup when looking in source code inside Marketo. Could this please be addressed?

1 Comment
Community Manager
Status changed to: Open Ideas