Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Craig Hewitt

    (@podcastmotor)

    Hi Anna,

    I’m not sure what the suffix after the .jpg is on your media file URL…the “?fit=1280%2C829&ssl=1 ” part. That’s what the feed validator is likely hung up on. The URL for your image file should be just the

    https://i2.wp.com/humanaturepodcast.org/wp-content/uploads/2016/11/1280px-Raven_Glacier_from_Crow_Pass-1.jpg

    If you enter that in I’d suspect that your feed will validate without any issues. Let us know either way.

    Craig

    Thread Starter annarader

    (@annarader)

    Hi Craig,

    I don’t know where to edit or enter this outside of the Seriously Simple Podcasting widget. I’m unable to find the XML file. I hope you can point me in the right direction.

    Thanks,

    Anna

    Plugin Author Craig Hewitt

    (@podcastmotor)

    Hi Anna,

    The iTunes image field populates automatically based on the image you select in the Cover Image field in the Feed Details tab of the Settings tab.

    I would suggest renaming the podcast cover image file on your computer and re-uploading it there. It should give you a cleaner URL, without the ” ?fit=1280%2C829&ssl=1 “. To ensure that the image is the right size you may need to resize it on your computer before uploading it.

    Thanks so much.
    Craig

    Thread Starter annarader

    (@annarader)

    Hi Craig,

    Thank you for your reply! However, the issue is that the images that are having problems aren’t the Cover image (aka the logo), but the all of images that we are using as the “featured image” for our podcast episodes on our website. I’ve re-uploaded one of those images, and that has not fixed the error:

    https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fhumanaturepodcast.org%2Ffeed%2Fpodcast

    I hope you can help me.

    Anna

    Thread Starter annarader

    (@annarader)

    Hi Craig,

    I really need some help and advice. This issue needs to be resolved as soon as possible. Switching to HTTPS is being required by iTunes for all feeds in January 2017. I’m unsure why changing everything to HTTPS would make the feed invalid and cause these image issues.

    I need to find a way to edit the XML file, which to my knowledge, I’m unable to do.

    I look forward to your response.

    Anna

    • This reply was modified 8 years, 2 months ago by annarader.
    • This reply was modified 8 years, 2 months ago by annarader.

    Please stop using validators for “normal” feeds. They were never made to read podcast feeds. CastFeedValidator is what you need. This validator says, there’s no error.

    Next step is: Go to iTunes Connect and change the URL for your feed to the HTTPS version. It should take about 10 minutes and then you know if it’s okay for iTunes.

    By the way: The image URL comes from the Photon module of JetPack. That’s the CDN image hosting service of WordPress.com. ??

    Thread Starter annarader

    (@annarader)

    Thanks Falk! That CastFeedValidator is fantastic! However, I’m also wondering if there is a way to edit the enclosure urls in the source feed? According to Podtrac (where we receive our mirrored feed that we place in iTunes) the issue is that the new feed from Seriously Simple Podcast with HTTPS, is still not valid. So, Podtrac won’t update their mirrored feed to HTTPS.

    A contact from Podtrac said: “It’s the enclosure urls in your source feed that need to be updated to use https. Right now they’re still http. We can not make any assumptions that it’s safe to change someone’s urls to https. We need the enclosure url to tell us that a particular media file is available via https before we’ll inject the https version of the Podtrac prefix.”

    Is this edit possible? I hope you can help me.

    Anna

    Thread Starter annarader

    (@annarader)

    I’m needing help with this! According to our contact at Podtrac, our feed that is put through Seriously Simple Podcasting (and then mirrored through Podtrac) needs enclosure URLS that are updated to HTTPS.

    Is this something that can be done? Our website has been updated to HTTPS, so I was assuming that the XML file would be updated as well.

    I look forward to help on this.

    Anna

    Thread Starter annarader

    (@annarader)

    According to our contact at Podtrac, our feed that is put through Seriously Simple Podcasting (and then mirrored through Podtrac) needs enclosure URLS that are updated to HTTPS.

    Is this something that can be done? Our website has been updated to HTTPS, so I was assuming that the XML file would be updated as well.

    I look forward to help on this.

    Anna

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Validation Error After Going To HTTPS’ is closed to new replies.