Email editor 2.0: variables in the text version

[Grégoire_Miche2]

One limitation of the new text editor; variables are only supported in the HTML version, not is the text one.

So let's say you want to use a variable for the title of the email:

<p style="font-weight: bold; font-size:16px;">${EmailTitle}</p>

This paragraph would just not show up in the text version, meaning that the title you have set in the variable will not shown up in the text version.

-Greg

[Anonymous]

I also agree. This is something that should really be fixed. When using those elements, they should be copied over to the text version. It is important as we are using them for our CTA button, Article Titles, and Descriptions.

[Anonymous]

Justin Cooperman​

Has there been any change in stance on this? Still not on the road map? Seems as though other users have a seemingly reasonable path forward re this challenge?

[Justin_Cooperm2]

It's still not on the roadmap, only because we don't have any changes planned to the email editor (due to the team's 100% focus on the new UX). Once we get parts of that rolled out, we'll be able to get back into the editors and make some of these improvements.

Justin

[Dan_Stevens_]

Now that we have officially deployed our new "all-in-one" template in Marketo, I'm now finally realizing what an issue this is.  The template uses variables extensively for things like editable hero banners, call-to-action buttons and URLs.  For example:

Produces a text version that will require manually editing every time:

Would really like to see Marketo address this and add it to the roadmap of "things that just don't work like they should".

[Grégoire_Miche2]

Hi Dan

Welcome to the fan club

-Greg

[Anonymous]

You can join us in scratching our heads as we wonder, "Why are new features being introduced when the old ones don't work quite right? Won't the new features have issues, too? Isn't that twice the issues? Aren't these features introduced to make things easier on us? If not, why bother? If so, why do they actually increase time spent?"

The world may never know, Dan. The world may never know.

[Grégoire_Miche2]

Hi Eric,

If you need more, read that post: Just do it! Marketo so-called minor missing features , together with this one :Email editor 2.0 is leaving room for a v2.1

-Greg

[Dan_Stevens_]

I meant to share these links as well, Greg.  These should be printed and pasted to the walls of the Marketo product team's offices!  Just run down these lists and check-off when each fix/feature is completed - and no new features until all the items here have been checked off!

[Anonymous]

Agreed. It is so frustrating to see Marketo release fundamentally broken features, then refuse to fix it, because they're busy...building more broken functionality.

[Matt_Ondo]

Justin Cooperman​, string variables are something we rely on heavily for CTA buttons since buttons are such an unstable element in email development. I totally understand this may be difficult to implement, could I ask for this to be added to the Email Editor 2.0 Overview nor Email Template Syntax documentation? Maybe one of those "Caution" callouts on the docs that states: "Only content within mktoText and mktoEditable regions will be translated into the Text-Only Version."