- This topic has 8 replies, 2 voices, and was last updated 10 years, 2 months ago by
.
-
Posts
-
For some odd reason, I have a background color that keeps changing on me in my confirmation emails. I have seen it display as two different colors so far.
My code is copied from my other RSVP mailings and they all work fine, but confirmation emails get this random background color. Crazy huh?
I will gladly post my code and screenshots if anyone is willing to help me with this, but this is so far out there that I thought I’d see if there are any volunteers first…
I only see this after the email is delivered. The html code before delivery looks great in the browser.
Any ideas?
Try saving the html from the mail in a file (on the pc where you saw the different color), and open that html. I’m guessing there’s some CSS issue in it that works on the server, but not remotely.
For the moment I’m not going to consider this as a EME bug 🙂I have done that and other extensive testing and my code is all fine.
I am getting down to the source though (I think) – hang on… 🙂
Ok, the background changes when I include this code in my confirmation email:
Your meeting registration for #_{F jS}[eme_if2 tag="#_{F j Y}" notvalue="#@_{F j Y}"][eme_if3 tag="#Y" notvalue="#@Y"], #Y[/eme_if3] – [eme_if4 tag="#F" notvalue="#@F"]#@_{F }[/eme_if4]#@_{jS}[/eme_if2], #@_{Y} (#_{l}[eme_if5 tag="#_{F j Y}" notvalue="#@_{F j Y}"] – #@_{l}[/eme_if5][eme_if6 tag="#_{F j Y}" value="#@_{F j Y}"] only[/eme_if6]), is confirmed.
It the system detecting #’s as the start of a hex color code? I don’t know why it would then apply the color to the background of the parent table cell…
Hmmm … your code got messed up I think. Try using the “code” button.
Also, try this for more easy-reading (no need to use eme_if4,5 or 6, and using #_STARTDATE and #_ENDDATE):Your meeting registration for #_{F jS}[eme_if2 tag="#_STARTDATE" notvalue="#_ENDDATE"][eme_if3 tag="#Y" notvalue="#@Y"], #Y[/eme_if3] – [eme_if3 tag="#F" notvalue="#@F"]#@_{F }[/eme_if3]#@_{jS}[/eme_if2], #@_{Y} (#_{l}[eme_if2 tag="#_STARTDATE" notvalue="#_ENDDATE"] – #@_{l}[/eme_if2][eme_if2 tag="#_STARTDATE" value="#_ENDDATE"] only[/eme_if2]), is <strong>confirmed</strong>.Edit (forgot to answer a bit): EME interprets what it can, and that get replaced by values, so you have to find which value doesn’t get interpreted …
Ok, thanks for your reply and tips! (Answered some questions)
I’ll see what I can come up with here.
Got it!
I had to convert all my #F’s and #Y’s into #_{F}’s and #_{Y}’s so that the system would not change the background color. My best guess is that one of the #F/#Y’s was triggering a hex color code.
Your meeting registration for #_{F jS}[eme_if2 tag="#_STARTDATE" notvalue="#_ENDDATE"][eme_if3 tag="#_{Y}" notvalue="#@_{Y}"], #_{Y}[/eme_if3] – [eme_if3 tag="#_{F}" notvalue="#@_{F}"]#@_{F }[/eme_if3]#@_{jS}[/eme_if2], #@_{Y} (#_{l}[eme_if2 tag="#_STARTDATE" notvalue="#_ENDDATE"] – #@_{l}[/eme_if2][eme_if2 tag="#_STARTDATE" value="#_ENDDATE"] only[/eme_if2]), <strong>is confirmed.</strong>Sounds a bit weird to me … maybe you were indeed hitting a borderline case here, but I see that you don’t use “ESC” in your tags and values, so the result is not escaped and maybe that is resulting in weird things …
Maybe.
A lack of ESC’s is due to the fact that I don’t understand why / when they are necessary. My code has always seemed to work and so I forget about ESC… But I’m not happy with simply leaving it there. I would prefer to understand because I hate coding something that is fuzzy! 🙂
- The forum ‘Generic’ is closed to new topics and replies.