My tokens are going whack! Styles set for tokens are displaying incorrectly.

[Anonymous]

Tokens that I've cloned are totally off in style and I can't get them to look right. They are not accepting the color and font size I select. They look right when setting them up, but when I preview them, they are left justified, wrong in color and size font, I'm not sure what's going on.

When I preview my email, the subject line that includes tokens looks like this:

Join Us for <div>November<br /></div>'s Webinar - <div>Mike's Knugget of Knowledge<br /></div>

Anyone having this issue? We've seen it for the last two months now and it's frustrating and wasting a lot of time figuring out how to fix it.

Not happy with Marketo lately, ever since the text editor changed we spend more time figuring out how to do things then saving us time.

[Justin_Cooperm2]

All - FYI, Linda and I chatted and we resolved this issue. There was a change made to the token editor (not text editor), that caused the "default root block" element of rich text tokens to be <div>.

So, if you created a new rich-tex token and typed "foo" you would get

<div>foo</div>

What was it before you ask? It was <p> , so if you typed "foo" you would get

<p>foo</p>

That doesn't seem much better but our engineers didn't realize we had custom code in place that, for single line rich-text tokens only, would strip out the <p> tags so you would end up with just "foo" in your subject line or in your landing page. That custom code was put in place several years ago to deal with customer confusing rich-text tokens and text tokens.

So, in the short term (within 7 days) I am having the engineering team revert rich-text tokens to have <p> as the default root block element so that single lines of text would still function essentially as text tokens. I also told Linda that we are adding a switch in the Admin page to let you control what the "default root block" elements are for the Landing Page editor, the Email editor, and the Token editor.

[Justin_Cooperm2]

This is now patched. The behavior has returned to using <p> as the "root block" element for program tokens.

[Anonymous]

Thank you Justin for your immediate attention to this matter, you were a tremendous help!

[Dan_Stevens_]

That's great news, Justin.  So this discussion ended up surfacing a hidden issue that probably would have become more problematic as time went on.  Thanks for raising this, Linda! (and pushing for a quick resolve, Justin!).

[Justin_Cooperm2]

Linda,

What do you mean by "cloning tokens"? Do you mean you have cloned a program that has my.tokens specified? Also, you shouldn't use a rich-text token in a subject line of an email. A rich-text token outputs HTML. You probably want to use a regular text token.

Tokens are unrelated to the new text editor. If you can provide more information I would be happy to help you. You can also email me at jcooperman@marketo.com

Justin

[Anonymous]

Hi,

Thanks for replying.

I setup tokens in the My Tokens tab at the highest level of the program, so that when I clone the program the next month, I just have to change the values and the data pulls through all my emails/landing pages, has saved me a lot of time typing it all in.

Yes, I use Rich Text token in the subject line. I'll try the regular text token, thanks for the suggestion. But I haven't had problems until now and we've been doing this every month since May of 2014 and we are now experiencing issues.

I sent in a support case and they are checking into it, I'll keep you posted if they can't figure it out.

Thank you!

Linda

[Dan_Stevens_]

I can 100% guarantee that by using a rich-text token in the subject line that the token value will also include the HTML like you showed above in your original post.  You absolutely must use plain old text tokens if your desire is to use this value in a subject line.  Like Justin said, this has nothing to do with the new HTML editor.

[Anonymous]

Thank you, I will try it. But it has been working for over a year. We have just seen the coding the past two months.

[Dan_Stevens_]

The only way this could have possible worked is if you had used a rich-text token and then stripped out all of the HTML, turning it basically into a text token.  At least you'll be using the proper type of token from here on out.

[Anonymous]

The coding for my token only had divs (<div>Mike's Knugget of Knowledge<br /></div>), which now displays in the subject line. I'm not sure why it didn't before. But yes, I'll change it to a regular text and test it, I'm sure that will work.

Thanks!

[Priyank_Joshi3]

If you want to fix Add to Calendar type token then you can directly include code in Hyperlink Text area with code "<span style="color: #5e5656; font-weight: normal;">Add to Calendar</span>" and this would give you the font style.

For your subject line token you can fix it with replacing Text type token.

Can you please share what type of token are you using? I think you are using Rich Text token in your subject line correct?

Thanks

Priyank

[Stijn_Heijthuij]

Hi Linda,

I've been hearing a lot of noise around the new Text Editor but haven't run into any problems like the ones you mention.

Can you provide some extra information? Like the values in the tokens, what are you trying to have displayed in which area of the email or landingpage?

[Anonymous]

Hi, thanks for responding. I'm using a Rich Text token and the values are things like Webinar Date, Webinar Time, so that it will display November, 19, 2015 - 10 am (PT) where I have the tokens throughout the program. It's worked fine in the past, we've just noticed issues last month and this month.

[Anonymous]

Hi, thanks for replying.

I've tried setting the font color, style in the Token editor and found it doesn't take, so I set the style to the token I enter in the email and it's worked fine in the past. And yes, I'm using a Rich Text token in the subject line.