Jonathan Bossenger

Hi @josephindiegraf

Based on your original post, I assume you’re working on a theme archive page, and rendering the series using the default WordPress series url (eg domain.com/series/series-name)

Your first step is to get the series object, which you can do using the following code

$series = get_term_by( 'slug', get_query_var( 'term' ), get_query_var( 'taxonomy' ) );

Once you have the series, you need to get the attachment id of the image, which is saved as term meta value for the series, using the meta key podcast_series_image_settings.

$attachement_id = get_term_meta( $series->term_id, 'podcast_series_image_settings', true );

Once you have the attachment id, you can use any of WordPress’ built in attachment functions, like wp_get_attachment_image or wp_get_attachment_image_src, which will return different types of data for that image, depending on what you need for your specific requirements.

https://developer.wordpress.org/reference/functions/wp_get_attachment_image/
https://developer.wordpress.org/reference/functions/wp_get_attachment_image_src/

Hi @sloantech

This might be related to this issue logged in our GitHub repo – https://github.com/CastosHQ/Seriously-Simple-Podcasting/issues/497

So far I’ve not been able to find anyone who could help beta test the fix though. If you read through the comments there, I’ve included details of how to join the beta, if you’d like to take part, please follow the instructions there.

Thanks

@heyforby after some further investigation, we’ve isolated a possible reason in the plugin why this could be happening.

Could I check if you’ve sent a ticket to hello@castos.com? If not, could I ask you to do so, I’d like to include you in a beta test for the possible fix.

Hi @heyforby

By default, all content types in WordPress are based on the default “post” type, and many plugins simply leverage the custom post type functionality. So for example any media files in the media library are actually stored as posts with the post type ‘attachment’, and any podcasts SSP creates are stored as posts with the post type ‘podcast’

The RSS feed for your SSP enabled podcast is generated every time the feed url is accessed, so the more episodes you have in your RSS feed (as set by your Syndication feeds show the most recent setting), the higher the CPU usage will be when the RSS feed is accessed.

There is an open ticket regarding this on the plugin repository – https://github.com/CastosHQ/Seriously-Simple-Podcasting/issues/435.

The short answer here is to either lower the number of items in your RSS feed, or look into some form of caching for the RSS feed, so that the site doesn’t have to run all the queries that fire every time the RSS feed is being accessed.

Alternatively, if you are hosting your files via your Castos account, consider using that RSS feed to power your Spotify show. We offer the ability to connect your RSS feed to your Spotify account, and the Castos RSS feeds are cached automatically, meaning less resources on your WordPress site.

Hi there, thanks for getting in touch.

It looks like there is a conflict or mis-configuration in either your hosting set up or your WordPress install somewhere that is causing this.

If I browse to the artwork link you’ve provided, I get the 404 not found error. However when I browse to your RSS feed, the image loads. (see screenshot https://www.awesomescreenshot.com/image/4998021/d4fa5187e5f224b3b41130c61f346d36)

When I copy the link from the RSS feed into my browser, the image url also loads. This is probably because it’s cached in the browser from the RSS feed. However when I attempt to refresh the original artwork link, I get the 404 error again.

Are you able to disable all other plugins, and just leave Seriously Simple Podcasting enabled, and see if the problem persists?

Hi @arminvit

You can use the ssp_episodes function for this.

This function will return a array of episode objects, that you can loop through and output as an unordered list.

I’ve included a simple example, which ouputs the episode title below

$episodes = ssp_episodes();
echo '<ul>';
foreach ($episodes as $episode){
	echo '<li>' . $episode->post_title . '</li>';
}
echo '</ul>';

Thanks, I will try to replicate this issue.

In the meantime, are you able to include a link to a a screenshot of the error you are seeing in dev tools.