deephouselounge or rclaessen (I don't know who I'm talking to in this thread, sorry)
Whom ever had the problem with
http://www.ipfridays.com/feed/podcast/ ...
The advice given to you was poor. First thing Todd or Mike should have told you is to use the following link to diagnose the problem:
http://create.blubrry.com/resources/powerpress/using-powerpress/diagnosing-feed-andor-player-issues-with-powerpress/Your feed is invalid. I looked at the feed (
http://www.ipfridays.com/feed/podcast/), it's a garbled mess. That is why Todd came quickly to the conclusion that something else caused the issue. He should have provided the link in the last paragraph at that point but he didn't, I'll slap his wrist later.
I looked at the HTTP headers and I notice something, WP-Super-Cache. I will not spend an hour explaining my opinion of WP caching plugins. I'll let you slowly grow your own opinion of them. What I can tell you is that caching a PHP application at the PHP layer does not solve the problem. It is true though "if" it adds lines to your .htaccess file it can perform better than pure WordPress, but doing so has another cost, your hair coming out when you have a problem like this one. If you have control of your server, install varnish, or sign up for a service like CloudFlare.
So how does one confirm the problem is not with PowerPress? Here's my trick, which works for most services where caching is enabled: add a query string to the URL in question, it will create a unique URL that is not already cached.
Cached:
http://www.ipfridays.com/feed/podcast/ (view the headers using plugin like HTTP Live headers in Firefox and see it is cached by WP-Super-Cache)
Not Cached:
http://www.ipfridays.com/feed/podcast/?random=12443545The not cached feed is valid and not messed up. This confirms PowerPress is creating the feed correctly.
My suggestion, either clear your WP super cache so it rebuilds, or stop using the WP caching plugin.
If you need us to fix this, we will gladly help; you via Gotomeeting during a consultation. Refer to Mike's previous reply on our consulting.