I fugure out with very tedious try & error, that the Expression Manager does not work consistent or at least expect different placeholders/expressions in the email-template and text-editor for all the other survey-places.

See Forum-Topic for Details: https://www.limesurvey.org/forum/design-issues/117048-email-template-if-statement-with-placeholder-token-does-not-work#177430

So, hulch ment:
«I don't think it is good in terms of compatibility and consistency to use ATTRIBUTE_1 in emails but TOKEN:ATTRIBUTE_1 in the rest of the survey.
Maybe a feature request? I think this might be considered a "feature" by developers, but you never know. »

For that I wrote an other report: https://bugs.limesurvey.org/view.php?id=14287
Also for missing documentation about detailed use of {if}-statement and the differences between use in email-template and other text for survey:
https://bugs.limesurvey.org/view.php?id=14286

But at the end, at least the button «validate expressions» in Expression-Manager and the code behind has a bug. Because with «wrong» Placeholder in email-template {TOKEN:ATTRIBUTE_1} there is NO «error marking».

But 1 step before, there must be a bug in the code. Because:

1. the "wrong" Placeholder {TOKEN:ATTRIBUTE_1} print_out the value from ATTRIBUTE_1.
2. At the same time, however, the IF clause is not translated and nothing print_out in email.

So the bug is The error/bug is either, because the wrong expression for email is output a value, or the wrong expression for email is not translated in the If-statement.
See for details topic in forum: https://www.limesurvey.org/forum/design-issues/117048-email-template-if-statement-with-placeholder-token-does-not-work

Both CAN NOT BE RIGHT.
Best would be to allow also {TOKEN:ATTRIBUTE_1} in email for backward-compatibility or stop to render the wrong placholder with {TOKEN:X} in front of for email-templates.

But WITHOUT an «error marking» in button «validate expressions» (see above), the correct use is absolutely undetectable. So Maybe the code behind button «validate expressions» has to change, if the error in the rendering-engine will not be fixed.

I hope this bugreport will help new users of limesurvey to get a more positive start in creating email templates or at least reduce the time needed for it massively.

chuicy regards
Martin