Back to Top

Problem with a atom feed

6 posts / 0 new
Last post
0xAFFE
Offline
Last seen: 2 years 2 months ago
Joined: 05/27/2012 - 05:41
Problem with a atom feed

I have a Problem with this feed:

http://warumnicht.dieweltistgarnichtso.net/feed.atom

I only get to display the HTML of the feed, but I can not download the enclosures.

I could see 2 possible Problems here:

  • There are more than one enclosures?
  • The first enclosure is oga (ogg audio) and maybe doggcatcher gets confused by the extension?

Thanks for your time and great Software!

eric
Online
Last seen: 1 hour 9 min ago
Joined: 11/06/2008 - 22:02
You're exactly right, those

You're exactly right, those two problems in combination are the cause. DC currently only supports the first enclosure for an episodes. For this feed, that is an html file.

We have it on the todo list to be able to pick which enclosure to download for an episode - http://mantis.snoggdoggler.com/view.php?id=478

Thanks for posting.

0xAFFE
Offline
Last seen: 2 years 2 months ago
Joined: 05/27/2012 - 05:41
The html-file is no enclosure

The html-file is no enclosure btw, the first enclosure is the ogg-file.

I have modified the xml a bit, so that only one enclosure is available in it:

https://bandenkrieg.hacked.jp/~tim/feed.atom

It seems to me that the rel attribute is not honoured?

eric
Online
Last seen: 1 hour 9 min ago
Joined: 11/06/2008 - 22:02
I mispoke earlier. My atom

I mispoke earlier. My atom parsing isn't looking for enclosures at all. This is actually the first I've heard of atom being used with enclosures.

I dug around a little and couldn't find any reference to the rel attribute as a part of the atom spec, however there are some that are using that as a convention. I created an issue for this.

http://mantis.snoggdoggler.com/view.php?id=1379

Thanks for posting.

0xAFFE
Offline
Last seen: 2 years 2 months ago
Joined: 05/27/2012 - 05:41
It is described
eric
Online
Last seen: 1 hour 9 min ago
Joined: 11/06/2008 - 22:02
Yup, I added a link in the

Yup, I added a link in the issue that points back to this post.

Thanks for digging up all the details.