email_content error in API

Highlighted
Developer

Re: email_content error in API

Highlighted
Moderator

Re: email_content error in API

Thanks, have a developer looking into this now.

Dave Berard
Senior Product Manager, Constant Contact
Highlighted
Moderator

Re: email_content error in API

Update from our engineering staff below.  Regarding the HTML5/CSS3 items, we don't have an ETA on the overal HTML5/CSS3 compatibility as a whole, especially because the spec for both of those standards is far from complete and still in comity.  However, we will definitely work on upgrading our support for any of the portions that are in a Draft Standard state according to IETF workflows. 

 

Examining the email_content attribute in the payload specified in the https://gist.github.com/anonymous/ef8c82cc63549ad90ac2

I noticed that the unescaped html content differed from the payload specified in https://gist.github.com/anonymous/68cca1409e78a6903f15.

 

In particular, the email_content html attribute did not seem to be proper html, with extra or placed incorrectly tags. 

 

This caused our html/css parser to choke and as a result, flag some errors that should not have occurred.

 

However, after testing with the valid html specified in https://gist.github.com/anonymous/68cca1409e78a6903f15, we did notice that our parser did lake support for certain

html5/css3 tags. For your particular payload, the style attribute that was causing issues was "border-radius". We are working to update our parser to enable more coverage 

of the html5/css3 attributes, and support for the border-radius tag should be coming soon.

Dave Berard
Senior Product Manager, Constant Contact
Highlighted
Occasional Participant

Re: email_content error in API

I'm experiencing the same issue. Email is content is valid HTML 4.01 Transitional per W3 Validator. Using PHP v2 SDK. With a minimal HTML body everything works but something in the newsletter is causing problems.

 

Json request is at : http://pastebin.com/zN7SkeMX

 

Any help would be much appreciated.

Highlighted
CTCT Employee

Re: email_content error in API

Hi Jessica, I'm trying to look into the issue that you are having, but it appears the Paste Bin is no longer valid. Can you repost that so we can take a look at it?

Highlighted
Occasional Participant

Re: email_content error in API

I've reposted it here : http://pastebin.com/gXHBZM23

Highlighted
CTCT Employee

Re: email_content error in API

What kind of error message are you getting? I've done some testing, and I'm not getting the error message

 

json.invalid.value.no_script_tags:#/email_content: Field does not support script content.

 

I am, however, getting this error message:

 

json.regex.mismatch.email_content

 

Which is most likely because instead of angle brackets e.g. "<" or ">" you have escaped your html. Your html should only be json escaped, as opposed to html and json escaped.

 

I made this change and did some additional testing, and it looks like we need to add additional support for html5 attributes like "vertical-align" on the "img" tag. I am continuing to investigate.

Highlighted
Occasional Participant

Re: email_content error in API

Thanks. I had been trying a few things since my original post one of which was escaping the HTML. I should have disabled that before sending the JSON data to you.

CTCT Employee

Re: email_content error in API

No problem!

 

Well, I was able to figure out what was causing our validation to fail based on your payload. Our validation was failing since it didn't support "center" for the "vertical-align" css attribute. We also had some issues with the meta tag as we didn't support the "name" attribute on that tag, and the value of the content "HTML Tidy for Linux/x86 (vers 25 March 2009), see www.w3.org" had some characters that we weren't supporting for this attribute.

 

I've updated our code base, and a fix should be coming out in the next couple days.

Highlighted
Developer

Re: email_content error in API

Still not working with this JSON:

 

https://gist.github.com/anonymous/a006365a217ebb73b1ee

 

I'm fed up. I'm not using your terrible v2 API anymore. I'm going back to XML since it at least works. This is just bad development. Why you feel you need to parse style tags is beyond me. Frankly, it's an embarrasment. 

Developer Portal

View API documentation, code samples, get your API key.

Visit Page

Constant Contact Would Like To Hear From You!

We want to hear from customers like you about your favorite features and how they have helped your business or organization. Tell us by answering a few questions in...

Read More
Featured