Can someone point out what might be...
Ed Spader
Ambassador
25 posts
I've had RED for months, but I'm only now sitting down to use it. My CMS allows for the sending of HTML emails and doesn't filter HTML (as far as I know). I just sent myself a test and you can see what I received in Outlook 2016 attached.
Brian Durfee
Senior Advisor
1,095 posts
My best guess is that your CMS is converting the text you see there to ascii characters instead of the original characters.
ASK ME ANYTHING
I provide personalized help for Coffeecup Users including personal or group training for Site Designer, Web Form Builder and more via Zoom.
Email me at support@uscni.org or call 865-687-7698.
Did you know that Web Form Builder can be used for both simple and complicated forms and that it's not limited to the default fonts and buttons? Take a look at a form we developed for WindowTinting.com.
https://forms.windowtinting.com/forms/w … ppingcart/
I provide personalized help for Coffeecup Users including personal or group training for Site Designer, Web Form Builder and more via Zoom.
Email me at support@uscni.org or call 865-687-7698.
Did you know that Web Form Builder can be used for both simple and complicated forms and that it's not limited to the default fonts and buttons? Take a look at a form we developed for WindowTinting.com.
https://forms.windowtinting.com/forms/w … ppingcart/
Frank Aiello
Registered User
3 posts
Hello Ed,
I have this exact same issue. I don't use a CMS so, I think the issue you are experiencing is not due to ascii conversion. I think it is a BUG in the software.
The code that gets generated is incorrect. In the code there are conditionals that check to see if the client displaying the email is Outlook and , if so, handle it correctly. However, the conditional code that RED is producing is not formatted correctly. See below:
SHOULD BE...
So, what is happening is that the code is not able to comment out the conditional correctly, therefore displaying it.
The temporary solution is to change every instance of
Hope this helps.
I have this exact same issue. I don't use a CMS so, I think the issue you are experiencing is not due to ascii conversion. I think it is a BUG in the software.
The code that gets generated is incorrect. In the code there are conditionals that check to see if the client displaying the email is Outlook and , if so, handle it correctly. However, the conditional code that RED is producing is not formatted correctly. See below:
<![if !mso]>
SHOULD BE...
<!--[if !mso]>
So, what is happening is that the code is not able to comment out the conditional correctly, therefore displaying it.
The temporary solution is to change every instance of
<![if !mso]>
to <!--[if !mso]>
, and you should be GTG. The real solution is that the developers address this and send out an update.Hope this helps.
Frank Aiello
Registered User
3 posts
The developers have kindly pointed out that this is called "Downlevel Revealed".
https://css-tricks.com/downlevel-hidden … -revealed/
And is necessary for Open Exchange Servers and OWA 365 email clients. However, when I test it in my Email On Acid account, it shows broken, as in Ed's original screenshot.
So, what to do?
https://css-tricks.com/downlevel-hidden … -revealed/
And is necessary for Open Exchange Servers and OWA 365 email clients. However, when I test it in my Email On Acid account, it shows broken, as in Ed's original screenshot.
So, what to do?
Scott Swedorski
VP of Software Development
0 posts
Have you tested with Litmus? In all our tests, I have never seen those conditionals appear as text with any version of Outlook, Exchange or 365.
Our latest newsletter viewed with Outlook 2016. Not a single <![if !mso]> appears.
I have also shared a public test with all versions of Outlook being used here at https://litmus.com/pub/99fa754
I would have to say the issue is with your email sending service. I will bet you they are making modifications to the markup.
If you can attach a sample project you have this issue with, I can run it through a few tests.
Our latest newsletter viewed with Outlook 2016. Not a single <![if !mso]> appears.
I have also shared a public test with all versions of Outlook being used here at https://litmus.com/pub/99fa754
I would have to say the issue is with your email sending service. I will bet you they are making modifications to the markup.
If you can attach a sample project you have this issue with, I can run it through a few tests.
Learn the essentials with these quick tips for Responsive Site Designer, Responsive Email Designer, Foundation Framer, and the new Bootstrap Builder. You'll be making awesome, code-free responsive websites and newsletters like a boss.
Frank Aiello
Registered User
3 posts
AHA!
I'd bet you are correct about the sending service making modifications to the markup. I'm going to make a simple test and send it directly to my EMail on Acid account from RED without using a sending service.
I do not have a Litmus account but, I think Email On Acid is attempting to do the same, in terms of displaying screen shots. I'll check back here with my results.
It wouldn't be the first time a service was butchering the code.
I'd bet you are correct about the sending service making modifications to the markup. I'm going to make a simple test and send it directly to my EMail on Acid account from RED without using a sending service.
I do not have a Litmus account but, I think Email On Acid is attempting to do the same, in terms of displaying screen shots. I'll check back here with my results.
It wouldn't be the first time a service was butchering the code.
Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.
