RSS Questions

There are no episodes in that feed. You haven’t posted any audio or video files for it to find. Podcasts have audio or video, not just normal posts.

Those weird javascript links are not good enough. You have to have links to the actual files themselves. I’m not familiar with podpress in specific, but without a link to the video file in the post, it won’t get included in the feed as an enclosure.

Podcatchers must find the actual file that they can download. They don’t do javascript.

Well, that’s kinda my question. I’m trying to find a plugin that will do the enclosure for me but apparently podpress 7.1 has a problem with WP 2.1, so I’m trying to find out if that is the cause.

Is there any way I can do an enclosure manually for now? Can I do something with the ‘custom fields’?

Also, do I need to do something with an XML file? I’m totally newbie to this part.

Enclosures are automatic. Just put a link to the actual files in the post itself. WordPress will figure it out after a while and add the necessary enclosures.

You know, something like this *in the post*:
<a href="https://example.com/podcast/video.m4v">Podcast #1: Video!</a>

That’s really all you have to do. Magic!

Of course, your server will have to have the correct MIME types set. You can do this yourself, just create a .htaccess in your root directory and add these sort of lines to it:
AddType video/mp4 .m4v
AddType audio/mp4 .m4a

And so on. Google the extension and “MIME type” to find out what the correct MIME type is for each file you include in this way.

hey, thanks a lot. That was a lot of help.

Is there any way to gain some control over automatic enclosures? And don’t two enclosures in one RSS item invalidate the feed?

When posting free music I tend to offer a variety of means to get at the file, but I would rather optimize the enclosures for podcasting to deal with one file or link in particular (i.e. get the MP3 not the WAV!…

Enclosures are actually implemented as a custom field, with a key of “enclosure” and a value of “URL\nLENGTH\nTYPE\n”. The \n’s are newline characters. Anyway, after an enclosure is processed, you should be able to see the enclosure in the Custom Field section of the Edit Post screen for that post.

And yes, you can have multiple enclosures in RSS 2.0. It may indeed break some readers, but the spec doesn’t actually specify it as zero or one.
Okay, so Dave Winer may disagree, but you know what? Screw him. If it’s not explicitly spelled out in the specification, then it’s not a legitimate argument. The simple fact is that all major blog tools allow multiple enclosures per item. ??

Most uses I’ve seen for multiple enclosures in podcasts involve having the same actual item but in different formats. As long as it’s the same content for the multiple enclosures, it still makes semantic sense.

Still, feed validator says it’s not valid, I grant you. So the solution is just don’t have more than one in there, if you want full compatibility.

Thanks, that was informative… and no, I am probably the last person to give a damn about compliance for the sake of compliance ??