New episodes won’t show on listening platforms

Hi, I had the same problem as you yesterday after the update. I rolled back the plugin, updated the episode and after a while the episode was released. Maybe some bugs. the developer will be able to tell us something more

Hi there, thanks for the message and for bringing this to our attention.

We’re not able to replicate this on our end with our test sites, so in order to help this could you share with us:
– What version of WordPress you’re running?
– What version of PHP are you running?
– Did you publish these episodes as Podcast post types or Posts or other custom post type
– Did you use the custom episode image feature (below the ‘Podcast file’ field in the “Podcast Episode Details” area)? Same for a featured image in the post.

With that we ought to be able to narrow in on what could be happening with this issue.

Hello and thanks for the reply. I publish podcasts directly as a New Episode in the Podcast section of your Plugin.

Last night I tried to insert the custom image of the episode in the section below the field to insert the url of the audio file.

I usually never do this, because I directly use the correctly scaled featured image for the Podcast, and therefore a square image of the same size.
After yesterday’s update, the episode was not recognized by the platforms. I rolled back, updated the episode, and the episode was released.

Could it simply be an update issue on the part of the platforms or does it hit the point that I put the custom image in the episode that I had never done before? I want to clarify that I have respected the dimensions and that is greater than 300×300.
The requested data are as follows:

Architettura del server Linux 3.10.0-962.3.2.lve1.5.39.el7.x86_64 x86_64
Server web Apache
Versione di PHP 7.3.23 (supporta valori a 64bit)
PHP SAPI fpm-fcgi
Variabile PHP max input 10000
Limite di tempo PHP 600
Limite di memoria PHP 3000M
Max input time 90
Dimensione massima di upload dei file 64M
Dimensione massima del post PHP 64M
Versione di cURL 7.72.0 OpenSSL/1.1.1h
SUHOSIN è installato? No
La libreria Imagick è disponibile? Sì
I permalink in chiaro sono supportati? Sì
Regole .htaccess Al tuo file .htaccess sono state aggiunte delle regole personalizzate.

Versione WordPress 5.6.2

@podcastmotor Thank you for the reply !
I’m using wordpress 5.6.2, php 7.2.34 and using lastest version of Seriously Simple Podcasting. I uploaded the episodes as a podcast post type (as seriously simple podcasting is pretty intuitive with this). And I didn’t put any image neither in the details neither in the post itself.

I also have an error message on the my dashbord, in castos news, saying “A feed could not be found at https://castos.com/blog/feed/; the status code is 403 and content-type is text/html; charset=UTF-8”

@semplicewebsite Thanks for the advice, I might use your way if we can’t solve my problem. But I think it’s better if you create your own topic if you need help. Maybe it’s easier for the plugin author. One problem at a time haha Però grazie, non mi sento più da sola con questo problema lol

@podcastmotor hi, some other informations if they can be useful.

I have these extensions active:
– Akismet anti-spam ver.4.1.8
– Buy me a coffee widget & button ver.2.7
– Podcast Subscribe button ver.1.2.8 (by secondline theme)
– rebusted! ver.1.1
– seriously simple podcasting ver.2.6
– seriously simple stats ver.1.2.10
– Twentig ver.1.2.6

Also, when I uploaded the last episode on monday, I hadn’t updated anything (neither wordpress or the plugin) and it already didn’t work. So I thought if I updated everything, it would work. And I didn’t have any problem with the first episodes

Thanks again for the help ??

Hi @clalala

Can I confirm, how many episodes do you have in your WordPress dashboard, on your RSS feed I can see two, épisode 1: défi cinéma avec Les Gar?ons sauvages et la Beat Generation and épisode 0: Spotify (un)wrapped

When I test this in the Apple Podcasts connect app, Apple also picks up two episodes.

https://tinyurl.com/yb8sekmd

@psykro hi ! yes I have two and I had a third one which I deleted because it didn’t work etc

@clalala if the feed is showing the correct number of episodes, and Apple Podcasts can read the data for those episodes, then it can’t be something in the plugin causing the issue.

The first thing I notice is that when I try to request your feed using the SSL version https://contrelabel.com/feed/podcast, there are some mixed content warnings in the browser (eg image being served via a non SSL secured URL)

Also, I ran your feed through castfeedvalidator, and there are some warnings there, which might be the cause of the problem https://castfeedvalidator.com/?url=https://contrelabel.com/feed/podcast

@psykro The thing is that I uploaded a new episode (which is now deleted) and it didn’t show anywhere, even after one whole day. And my podcast even disappeared from some platforms for no reason. I did as I have always done before but it didn’t work.

I also ran my feed through castfeedvalidator. For exemple, it says that the lack of id3 tags is causing an error but when I contacted Blubrry themselves, searching around for help, they said that no one uses id3 tags anymore and that it’s not a problem. So I don’t think castfeedvalidator is that reliable.

But I’ll play around with last updates, other extensions that might interfere in a way or another (even if I don’t see how it could be related). I’ll also make some research about that SSL thing which is totally beyond me honestly haha

In any case, thanks for the help !

I ran into a similar issue, except I was simply editing an existing episode. After editing it, I went to the episode’s page and found that the player didn’t play the episode. So I went back to the episode editing page to make sure I hadn’t mistyped the url of the mp3, and found that the podcast url had been replaced by the url of the podcast cover image I had tried to add. Seems like the JS for the “upload new image” button modified the contents of the “podcast file” field. I changed the URL back and everything was fine.

Hi @mmxxiii thanks for the details here. We’re looking into this and a potentially related issue as we speak and ought to have a plugin update ready shortly that will take care of this. will be in touch as that progresses from our end.

If we can do anything else just let us know.