Feedburner Not Recognising MP3 files in Wordpress Podcasting Blog
August 6, 2008
A frustrating week. I have just spent the best part of a it working on a problem since upgrading podcasting blogs from 2.5 to 2.6 or installing podcasting blogs on wordpress 2.6. I just wanted to share the experience so that no one else feels my pain.
If you are a wordpress hosted podcasting blog user either installs wordpress 2.6 or upgrades from 2.5 to 2.6 and you find your podcast breaks in any of the following ways
- feedburner no longer recognising mp3 attachements in your feed
- podpress plugin player no longer working
- can’t submit podcast to iTunes
- feedburner error message “Content Type reported: text/html; charset=UTF-8
Media enclosure not created because: The content type returned from your host server was a text type, not a binary media type. Podcast content should always return a binary media type, such as audio/mpeg for audio, or video/mpeg for video.\”
Then try applying the ‘No Revisions’ plugin from http://wordpress.org/extend/plugins/no-revisions/ and your problems should go away.
What is wierd about this problem is that I experienced it on one web host and not another, so not sure what is going on there.
Here is the text from the No Revisions site which explains what it does “While the WordPress 2.6 upgrade has not gone smoothly for a lot of people, one new feature that has yet to bite too many people is post revisions. Whenever you save a change in a post in WordPress 2.6, it saves a copy of the old version as well as your changed version. If you a lot while writing, that can add up to a lot of extra crud in your database.
Now, these can be turned off by editing your wp-config.php file, but that’s a bit gross for a system like WordPress where everything else can be done through a nice web interface. This plugin gives you that web-based solution.
Just install and activate this plugin and no more revision debris in your database. Of course, that also means no safety net if you accidentally screw up a post and then save it, but that was the case until 2.6 anyway.”
I hope this helps.
Regards, Greg







