Hugh Lashbrooke on "[Plugin: Seriously Simple Podcasting] URL feed not working, redirecting to download"

Hey guys, today my RSS URL feed stopped working and therefor my podcast doesn't work in iTunes or other apps, it only works on my site (that works fine).

When trying to access the URL: http://sjolivet.se/feed/podcast
it starts to download the file instead. I can't locate the problem either. I´ve done nothing different from earlier episodes so I think it is somewhere within the plugin?
Can you please help me with this problem?

At first I though the problem was that I didn't have the latest version but when I updated the problem was still there. =(

My site is: http://www.sjolivet.se

https://wordpress.org/plugins/seriously-simple-podcasting/

I think the problem was within the post connected to the podcast. I don't understand why my RSS feed ain't showing in my browser though. Is that something the browser itself (Chrome & Safari) stopped doing?

I'm having the same issue on my end! The URL: humanaturepodcast.org/feed/podcast starts to download instead of open up the feed. Why is this happening? Will this affect my feed?

Seems to be a WordPress 4.5 related problem: I downgraded back to 4.4.2 and the error disappears.

But it's only a visual flaw: Feedreaders still seem able to access the podcast xml data.

Thanks for the info Falk - I'll look into what caused this in WordPress 4.5 and see if I can work around it.

Chrome Developer Tools say:

Resource interpreted as Document but transferred with MIME type application/octet-stream: "...".

Hope that helps a bit?

Yeah - I've noticed that myself. Will find a work around for this ASAP :)

Stopped working for me in Chrome as soon as I updated to latest plugin version (unless a strange coincidence) but have been setting up a new podcast over last few days so in and out of wordpress pages and viewing feed often. Feed seems to be processed fine by readers though and only prompts for download in chrome. Edge and firefox in my brief testing seem ok?!

I'm working on a fix for this, but the good thing is that it is not affecting feed readers (iTunes, etc.) - they are still processing feeds just fine. The issue only comes in when people try to view the feed in the browser.

I'll have a fix out as soon as I can :)

This is fixed in the latest release (v1.14.6).