Hi there,
I have just release v1.8.1 that includes the option of whether to position the audio player at the top or bottom of your post content. Thanks for the suggestion.
The date display will be the same as for your standard blog posts – this plugin does not use any special templates, so it will display that information in the way that your theme dictates.
Cheers,
Hugh
Thread Starter
alarch
(@alarch)
Wow, I’m impressed with your prompt response and action. Thanks for that, the update works really well.
As for the dates being displayed issue – I’ve created a normal “Test” post, and this displays the date on the blog page, unlike the podcast posts. The website, in development, is here: http://www.podcastpeldroed.co.uk I’m using the Sparkling theme.
Note the absence of the “Argentina Friendly” embedded podcast from the list of Recent Episodes, in the sidebar. This was created as an episode, but lacks an entry in the Audio file: field, because the embed code is located in the text entry field.
As you can see nothing displays under Archives in the sidebar. I guess this is because the episodes aren’t recognized as posts.
Hope I don’t seem too greedy here…
I’m not too sure why the date isn’t displaying correctly for you. Like I said – this plugin doesn’t touch that side of things at all, so your theme will be handling that.
As mentioned in the other support thread you opened – the plugin isn’t currently setup to cater for episodes that don’t have an audio file saved. This means that the widget will only display episodes that have that file attached to them. I’m working on a way around this at the moment and will update you once I have something.
Thread Starter
alarch
(@alarch)
Thanks again for the prompt response and for looking into catering for episodes without an audio file saved. I’ll have a dig into the theme files to see if I can come up with an answer.
Thread Starter
alarch
(@alarch)
I’ve managed to modify the content.php theme file (placing the modified file in my child folder) – and the episode meta details are now displaying fine in the blog. Just a one line change needed.
