Hey @BigData HOSBEC oh, that’s so strange! I am assuming you’re using the “New Campaign” trigger for MailChimp, is that correct? If so, and you look at a recent run from your Zap History, so you see this HTML coming across within the Trigger data?
If not, do you see it in the Wordpress Post output within the run? That should give us some insight as to which step of the process might be adding this and what our options are for moving forward!
Hi @jesse , thanks for your quick response!
Yes, I am using the “New Campaign” trigger in Mailchimp and the “Create Post” action in WordPress.
The data (html) out from MailChimp doesn’t look exactly like the code ive added before, but it’s as follows:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<!-- NAME: 1 COLUMN - BANDED -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>*|MC:SUBJECT|*</title>
Exactly the same code is shown in “archive_html” from MailChimp and in the “ content” recieved in Wordpress.
While the raw content stays exactly with this code, the “rendered” content from the (Data out) section in my Wordpress zap introduces the problem and changes the code to:
<p><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<!-- NAME: 1 COLUMN - BANDED --><br />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<title>*|MC:SUBJECT|*</title></p>
Is there anyway to set how the content is being rendered to avoid extra spaces or paragraphs?
Thanks!
@BigData HOSBEC Ahh, I see - thanks so much for those screenshots! It’s clear on where the issue is. However, I’m not sure why that is happening. For this one, I am going to suggest contacting our support team so they can look into some logs and get to the bottom of this. You can get in touch with them using the form here: https://zapier.com/app/get-help
We’ll be following along but please do keep us posted if you manage to get this resolved in the meantime!