José Sena

I did everything you said (in fact, I did it all yesterday).

After I cleared my server and browser cache, I tried to make a new install on my server (with nothing but SSP) and still got the same error. Tried with a fresh install on my local machine and the error was the same.

My point with the original feed thing was that if the problem was my database or my theme behavior, the original feed should be damaged too, but it was not the case in both tests.

The only way I could get the plugin working was using a install with ONLY episodes. If I post something else… BOOM. For using the SSP feed I did a “mirror” install to use just the feed. It’s not the best way but works for me. Just giving the feedback because it can help other users. Again, I did all the tests possible, local and remote, so I really don’t know what it could be.

I love your plugin and hope it continues being improved.
Again, sorry about my english and thanks for your attention.

Disabled all my plugins and nothing.

If the problem is with my theme, another plugin or anything else but the SSP, why is the original feed ok?
If you look at https://galpao42.com/podcast/feed/ you’ll notice that the feed is actually getting the right post data. If the issue was caused by any other thing but the SSP, it would be broken too.
BTW, tried to repair my database and it was fine.