Back to Top

Ampersand causing DoggCatcher ver. 1.2.4149 to deny the feed

5 posts / 0 new
Last post
Nafcom
Offline
Last seen: 2 years 2 months ago
Joined: 01/17/2018 - 13:08
Ampersand causing DoggCatcher ver. 1.2.4149 to deny the feed

Hi there, we have had a report by one of our podcast listenners, that it appears that the Ampersand causing DoggCatcher ver. 1.2.4149 to deny the feed.
It appears to be in our latest podcast release #42 (as the time of writing this at line 17) Source: http://feeds.feedburner.com/sceneworldpodcast
While this is not 100% W3C propper, DoggCatcher is really the only one not accepting an ampersand (We are listed in 50+ podcast direectories including iTunes and we periodically check each time we release a new episode that it publishes trouble free)

I cannot simply change this, as this will cause double entries in some of the podcast directories we are listed in as some do not detect re-published episodes resulting in doube database entries.

Please supply a fix. Our listener uses Android with DoggCatcher ver. 1.2.4149 (I am iOS user myself and cannot really verify but the error message he gest is

"Error loading feed: java.lang.Exception: URL is valid, but it doesn't look like a valid RSS feed: org.apache.harmony.xml.ExpatParse$ Parseexception: At line 17, column 100: not well-formed (invalid token)"

Thank you very much in advance!
Cheers!
Joerg

WayneC
Offline
Last seen: 1 week 5 days ago
Joined: 02/23/2011 - 22:28
Scene World Feed

The Scene World feed has some issues according to the Feed Validation Service https://valiScene Worlddator.w3.org/feed/

This feed does not validate.

line 17, column 100: XML parsing error: :17:100: not well-formed (invalid token) [help]

In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendation.

line 10, column 101: Self reference doesn't match document location [help]

... rel="self" type="application/rss+xml" />

The latest published episode "Podcast Episode #42 - AmeriCon Special" was released on Dec 28, 2017.....The app (DC) relies on RSS URL's provided by publishers...other podcast managers may cache media from previously published podcasts on their own servers and currently not possible with the app.

So in order for the app to access previously published and new episodes from Dec 28, 2017 on, the current errors have to be resolved by the publisher of the feed.

Nafcom
Offline
Last seen: 2 years 2 months ago
Joined: 01/17/2018 - 13:08
I did resolve the ampersand

I did resolve the ampersand issue. The "... rel="self" type="application/rss+xml" />" I cannot as this is created by Feedburner. Google stopped all further development and closed down the support in 2012, there is no way otehr than community support. I will start a thread there too but my hopes are low. So I can only resolve the main issue and will check back with our listener and hope this will resolve it for him. If not, I am afraid we rely on your further help.
Cheers!
Joerg

Nafcom
Offline
Last seen: 2 years 2 months ago
Joined: 01/17/2018 - 13:08
I just ran the validator

I just ran the validator again and this also fixed the 2nd "self" issue" hooray! :)

https://validator.w3.org/check?uri=http%3A%2F%2Ffeeds.feedburner.com%2Fs...

Cheers!
Joerg

WayneC
Offline
Last seen: 1 week 5 days ago
Joined: 02/23/2011 - 22:28
Cool!

Cool! The feed is working now