Custom field enclosure
-
I found that something had created a custom field called enclosure with the following value:
https://redlightmusic.com/wp-content/uploads/el-tintero-001-shalako-dec-2008.mp3
82433381
text/plain
a:5:{s:6:”format”;s:10:”el-tintero”;s:8:”keywords”;s:0:””;s:6:”author”;s:7:”Shalako”;s:6:”length”;s:5:”57:15″;s:8:”explicit”;s:3:”yes”;}I have been experimenting with the Podcast-Channels plugin and haven’t seen a custom field for enclosure since I deactivated the Podcasting plugin. iTunes was seeing my episodes before this custom field appeared.
I copied the value of the enclosure and deleted it. Resynced Feedburner. Then iTunes said “there are no playable episodes”.
In the past I’d seen enclosure as an option in the add new custom field name drop down, but it wasn’t there. I tried typing ‘enclosure’ in as a custom field name and pasted the above text in for value. Resynced Feedburner. Now itunes sees the episode again.
Questions:
1. I’d love to know under what circumstances a custom field for enclosure is created. It doesn’t seem to be consistant.
2. Can someone also please point me to a spec for this enclosure syntax?
3. Looking over the enclosure value, I notice text/plain. Before I deactivated it, the Podcasting plugin used to complain that the mp3 file was being reported as text/plain when it should be audio/mpeg. I added ‘AddType audio/mpeg .mp3’ to my httpd.conf and restarted apache but this didn’t resolve the issue. Although I’m no longer using the Podcasting plugin, it appears that this file is still being reported as the wrong file type. How to fix?
- The topic ‘Custom field enclosure’ is closed to new replies.