I’m trying to move my current web platform over to Ghost, and have hit some trouble with audio files for a podcast feed.
Looking at the available documentation, it seems like the only way to have a syndicateable RSS feed is if you host your audio files elsewhere, then just link them in a hacked metadata field. Is that right?? I feel like I must be missing something as it’s so clunky compared to the rest of Ghost…
What I’d like to do is link the audio file in the RSS feed from an audio card on the post, ideally directly in the Handlebars template, but not-so-ideally by finding the URL and adding it to the Facebook Description field, as per the doc above. Are either of those possible?
Podcasting is quite a big part of my content and splitting it out onto a different platform is very much something I want to avoid.
Hi Matthew,
I’m curious to know what you did for this?
You do appear to have misunderstood the documentation a bit though, the Facebook Description field is just to get the MP3 file URL into the feed:
<enclosure url="{{og_description}}" length="0" type="audio/mpeg"/>
So it can be a file local to your Ghost, or hosted elsewhere.
Personally I’m very disappointed, I was under the impression that Ghost was podcast friendly. Having to use a custom template, with hard coded and inaccurate fields (that would fail validation), and then a kludge to work around a limitation does not equal friendly.
I’m going to contact Support to confirm, but right now I’m planning to use a script on another server to pull in my Ghost RSS feed and push out a valid podcast feed from there.
1 Like
I thought that using the og_description was a pretty bad hack, too. I’ve set up a client with a cloud function that reads his posts, extracts the audio file (hosted on Ghost), and modifies the post to store the necessary enclosure information in code injection. It works, and I think it’s a better solution than what the current ‘podcast’ themes do, but it does require that external cloud function. Making it available as a plug-and-play hosted service is on my roadmap. Hoping to get it done later this month or early next.