Title: JSON API – Issues with iframe and draft content
Last modified: August 31, 2016

---

# JSON API – Issues with iframe and draft content

 *  [Jeff Lambert](https://wordpress.org/support/users/lambje/)
 * (@lambje)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/json-api-issues-with-iframe-and-draft-content/)
 * Hello,
 * I’m using a branch copy of the automattic syndication v2 plugin and have recently
   started getting errors in two situations. Both were working previously. Both 
   symptoms are the same.
 * We have a centralized multi-site where we author and curate our posts and uses
   syndication v2 for posting new content out.
 * We have a stand alone install that uses JetPack JSON API to receive posts inserts/
   updates.
 * What we are seeing now is that saving a new post as draft does not push through.
   In looking at the syndication log the message that comes back is “Whoops, the
   provided date is invalid.”. I can publish a post and then change the status to
   draft and it will create the post on the remote site and, subsequently, change
   the status to draft. That’s one of our current work arounds. The other is that
   it seems that when you do finally publish that this will push through.
 * The other issue we have is that if there is an iframe in the post content, it
   won’t synch out at all. If you previously pushed it and then add the iframe the
   update will fail. The message back from the post in both instances is as follows:
   The Jetpack site is inaccessible or returned an error: transport error – HTTP
   status code was not 200 (403) [-32300]
 * I, obviously, would like to remedy these issues.
 * One other things, since I’m here, I can send a post to trash on the publishing
   site and this will push through but a permanent delete will not. We’ve just ignored
   this and manually cleaned up but this, to me, seems like a defect too.
 * [https://wordpress.org/plugins/jetpack/](https://wordpress.org/plugins/jetpack/)

Viewing 1 replies (of 1 total)

 *  Plugin Contributor [csonnek](https://wordpress.org/support/users/csonnek/)
 * (@csonnek)
 * Happiness Rocketeer 🚀
 * [10 years, 3 months ago](https://wordpress.org/support/topic/json-api-issues-with-iframe-and-draft-content/#post-7381339)
 * For the “Whoops” error, that’s straight from WP core
    [https://github.com/WordPress/WordPress/blob/ff37a3b7306009e7591a6bedcdfaf376953c239b/wp-includes/post.php#L3179](https://github.com/WordPress/WordPress/blob/ff37a3b7306009e7591a6bedcdfaf376953c239b/wp-includes/post.php#L3179)
 * Regarding the rest, I asked a colleague of mine and they said:
 * > I’d guess that something is sending the date wrong. I’m not sure how Jetpack
   > is involved in that piece of his setup though.
   > For the iframe error, the error is a 403 from his server so have him go check
   > the error logs; most likely something on his server is blocking the iframe.
 * Regarding the last issue, I’d recommend opening up a new issue on the Automattic
   GitHub repository for the syndication plugin so they can take a closer look.

Viewing 1 replies (of 1 total)

The topic ‘JSON API – Issues with iframe and draft content’ is closed to new replies.

 * ![](https://ps.w.org/jetpack/assets/icon.svg?rev=2819237)
 * [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/jetpack/)
 * [Active Topics](https://wordpress.org/support/plugin/jetpack/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/)

## Tags

 * [iframe](https://wordpress.org/support/topic-tag/iframe/)
 * [transport error](https://wordpress.org/support/topic-tag/transport-error/)

 * 1 reply
 * 2 participants
 * Last reply from: [csonnek](https://wordpress.org/support/users/csonnek/)
 * Last activity: [10 years, 3 months ago](https://wordpress.org/support/topic/json-api-issues-with-iframe-and-draft-content/#post-7381339)
 * Status: not resolved