Title: [Plugin: podPress] Feed not validating
Last modified: August 21, 2016

---

# [Plugin: podPress] Feed not validating

 *  [prosborne](https://wordpress.org/support/users/prosborne/)
 * (@prosborne)
 * [12 years, 10 months ago](https://wordpress.org/support/topic/plugin-podpress-feed-not-validating/)
 * I have added this plugin to our site, but when supplying our feed url to iTunes
   or validating it, we get the following errors:
 * >  erver returned HTTP Error 404: Not Found [help]
   >  line 1, column 0: XML parsing
   > error: <unknown>:1:0: syntax error [help] Bots get the naked version
   > In addition, interoperability with the widest range of feed readers could be
   > improved by implementing the following recommendation.
   >  Feeds should not be served with the “text/html” media type [help]
   > Source:
   >  Bots get the naked version
 * We have a valid feed for the rest of our site, but when we try and generate one
   at a new URL just for iTunes, I can see all of the formatting is there but it
   shows up as xml 1.0 and doesn’t validate.
 * We have a few items entered as posts, but have them set to private. Would that
   make a difference? Also, we have the actual player disabled on them as we are
   using our own player on our website.
 * Anyway, this is my first time using this plugin so I am a little lost on where
   to start. I have read around and seen people that have had similar problems but
   when I try and change the filter settings to get some <item> tags I don’t end
   up getting those specific tags and my XML version remains 1.0.
 * Thanks!
 * [http://wordpress.org/extend/plugins/podpress/](http://wordpress.org/extend/plugins/podpress/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Thread Starter [prosborne](https://wordpress.org/support/users/prosborne/)
 * (@prosborne)
 * [12 years, 10 months ago](https://wordpress.org/support/topic/plugin-podpress-feed-not-validating/#post-3924828)
 * So I made some of the content live and that fixed a lot of the errors. I am still
   having issues with iTunes downloading the videos. We are using an Amazon S3 bucket
   to store the videos. Do they have to be local to show up in iTunes? Thanks –
 *  Thread Starter [prosborne](https://wordpress.org/support/users/prosborne/)
 * (@prosborne)
 * [12 years, 10 months ago](https://wordpress.org/support/topic/plugin-podpress-feed-not-validating/#post-3924878)
 * So it is not sending the S3 link for the video but serving a local file as the
   URL in the feed. That URL doesn’t go to anything so the iTunes is getting a 404
   error. I just need to know how to make sure that the S3 link is correct.
 *  Plugin Author [ntm](https://wordpress.org/support/users/ntm/)
 * (@ntm)
 * [12 years, 10 months ago](https://wordpress.org/support/topic/plugin-podpress-feed-not-validating/#post-3925042)
 * regarding the feed problems: It would be great if you could tell me the name 
   of your blog (or maybe the feed URL).
 * regarding the S3 URLs: iTunes recognizes media files only if the URL ends with
   a typical file name with a file name extension of one of the supported file types
   like .mpg or .m4a. If the S3 URLs end just with a lot of alphanumeric characters
   then it does not recognize the video as real file.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘[Plugin: podPress] Feed not validating’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/podpress_f79938.svg)
 * [podPress](https://wordpress.org/plugins/podpress/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/podpress/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/podpress/)
 * [Active Topics](https://wordpress.org/support/plugin/podpress/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/podpress/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/podpress/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [ntm](https://wordpress.org/support/users/ntm/)
 * Last activity: [12 years, 10 months ago](https://wordpress.org/support/topic/plugin-podpress-feed-not-validating/#post-3925042)
 * Status: not resolved