![]() ![]() While I understand that this is probably expected behavior in gPodder and a bad decision on the part of the feed's authors, could it be possible to relax the criteria for unique items in the database, so that the an unique url in the tag is enough, instead of the tag / combination of the two (when the tag is not present)? After all, the iTunes webpage ( ), has no problems listing all items from the same xml also the feed parses fine in some other podcatchers / programs with podcast functionality that I tried, like Grover, or AIMP, as it seems they do not check for unique tags, only. The xml with the tag removed from all (still without item guids) parses / saves in the database just fine, because there is no duplicity. Looking back, the visible episodes are only the last ones from these storylines. For example, the oldest five episodes all have in (now 404), and unsurprisingly, only the last of the five (inverse order) gets saved to the database, others get discarded as duplicates / throw the error. The individual episode urls in, as well as other relevant item tags, are unique though. ![]() After looking further into the xml file, it looks like the authors of the feed decided to add an identical tag to a few consecutive items in the feed at a time, denoting an individual storyline. I don't think missing the (arguably optional) tag for is the issue, I subscribe to many rss feeds without those tags for items, and they parse just fine in gPodder. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |