Generally speaking, I am okay with the new "beta" Custom Code Editor (CCE), but I do have something odd that has happened with one campaign in particular. When the first email went out, the system seems to have changed the primary cell background color from white to bright blue. When I view the email in DreamWeaver, it appears normal (white). When I upload the code to my website (for the web version), it appears normal. When I use the old/current CCE, it comes through as intended. But something gets dorked in the new CCE that changes the colors.
The code is provided to me by the client, and the only thing I edit is to add a <meta> for a link to the web version I host. I will attach a link to their code as well as a link to the web version and the ones sent by ConstantContact. Hopefully someone can take a peek under the hood and see if there is some broken piece of code or other obvious error that might lead to the new CCE misinterpreting what is intended.
Original/untouched source code from client: https://www.charlestonvirtualhomes.com/flyers/1269Hamlin_sourcecode.txt
Sample blast using the old CCE: https://conta.cc/39rzt89
Sample blast using the new CCE: https://conta.cc/30N9h45
Hopefully someone from the in-house dev team will read this and find the issue(s) and share a solution or fix the new CCE to prevent this from happening before full implementation.
Thank you for reaching out to the Community! I appreciate all the information you have provided us and I am escalating your case to my advanced technical team so they can do additional research on this and get back to you as soon as possible. Thank you!
I wish he would have replied because the custom code editor is truly messing up established HTML pages/coding that were in templates....
Constant Contact doesn't care that they change things that mess up the businesses/operations of its customers -- it just wants to makes "something new" without caring about how it hurts the people who actually use the system - terrible job.
It appears based on the case from last year that it had something to do with the [if mso] tags not being functionable in the current custom code editor. If you absolutely must have the [if mso] tags in your coding, you can use this link to access the legacy custom code builder (assuming you're already logged into your account). If you don't believe the issue is an incompatible [if mso] tag, please call our general support so they can get you to our higher level technical team for more live, 1:1 troubleshooting.
Thank you! My code did not have any [if mso] tags, but using the legacy custom code builder worked!
Are they still going to work on this issue with the new custom code editor?
If your issue wasn't an [if mso] tag, then I'd still encourage you to call our general support and work with the T2 team to see what the issue is, as that can greatly assist them in addressing whatever the problem is.
Also, the legacy custom code builder keeps booting me out and trying to get me to use the new editor, so I can't complete setting up the email and testing....so this won't work
"Authenticating your emails is the best way to ensure your emails achieve maximum deliverability. If you have your own domain, setting up self-authentication is especially important! " - WillSee Article
"Target your most engaged contacts by creating a segment. Create a special offer or show your appreciation!" - CaitlinSee Article
"Did you know? You can send unlimited test emails to your verified email address, but only 50 in a 24-hour period to non-verified email addresses." - NickSee Article
The holidays have come and gone. For many seasonal businesses, this means the rush of shoppers has decreased as well. Instead of turning off the lights and waiting for spring, make your email marketi...See Article