Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Hugh Lashbrooke

    (@hlashbrooke)

    That’s odd because the audio file details in the feed are from your podcast episode, but the title and content are from your blog post. That indicates that the issue isn’t actually with SSP, but rather with your site itself. It could be another plugin, or possibly your theme that is causing the issue, but whatever it is, it is getting your database somewhat muddled by sending the wrong data.

    You may need to do a database repair (here’s a guide on how to do that), but it could just be that another plugin is causing a conflict.

    Either way, this kind of thing is outside of the scope of this plugin as there’s no way this would be possible with how the SSP feed is setup.

    Cheers,
    Hugh

    Thread Starter José Sena

    (@jose42)

    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.

    Thread Starter José Sena

    (@jose42)

    Disabled all my plugins and nothing.

    Plugin Contributor Hugh Lashbrooke

    (@hlashbrooke)

    The ‘original’ feed is merely the built-in post type feed that WordPress core provides. It is not suitable for podcasting as it does not contain all of the necessary data the iTunes and other services require. The custom feed that SSP generates uses a standard WordPress query to fetch all of y our podcast episodes.

    This query just uses the standard get_posts() function from WordPress core, so if the posts are being returned incorrectly like this then there will be something else interfering with that query.

    Even if you disabled all of your plugins, the feed data could still be cached on your server and in your browser, so you’ll need to disable all of your plugins (and preferably revert to a default WP theme, like Twenty Sixteen) and then clear your server cache and browser cache. That way you will be able to do a proper test.

    It may look like I’m just trying to shift blame away from my plugin, but I can assure you that there is no way that the results you’re seeing are caused by SSP itself.

    Thread Starter José Sena

    (@jose42)

    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.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Feed showing blog posts instead of podcasts episodes’ is closed to new replies.