NOTE: This post is a pure podcasting nerd-fest. If that's not your thing, feel free to move on.
I help run two podcasts published using the fine open-source blogging software WordPress. A few months ago, when the latest version of WordPress, 2.6, came out, I immediately upgraded one of the sites, Inside Home Recording (IHR). Whoops. Mistake. The new version broke the key podcasting plugin we use, podPress.
So I held off upgrading the other podcast, Lip Gloss and Laptops, keeping it at WordPress 2.5 to maintain compatibility while waiting for a podPress upgrade. Over at IHR, where it was too late, I instead installed the new Blubrry Powerpress podcasting plugin as a substitute.
UPDATE 21 Oct 2008: For those of you using the Blubrry Powerpress plugin, there is a new update that fixes the problem I talk about below, which Angelo discusses in the comments. His summary: "We've just made a new version (0.4.0) which now displays an image in place of loading quicktime files. We use a simple blubrry play icon as the default play image, but you can provide your own play image by adding a custom define to your wp-config.php that includes the URL where your custom play image is located. This new option is documented at the bottom of the Advanced Tweaks page for the Blubrry Powerpress plugin." Kudos to the Blubrry team.
Now, Powerpress is fine. It does the job, and recognizes most of the detailed settings from podPress, but it doesn't offer as fine-grained control, and has one major problem: for non-MP3 podcasts, such as the Enhanced AAC files we use at IHR, it puts up a little movie player (as does podPress), but in doing so (unlike podPress) it also starts loading the podcast file whenever someone visits the web page. For pages with a lot of podcast episodes on them (like our AAC episode index, or even our home page), that really slows down page load times, wastes bandwidth, and throws off audience statistics.
So I wanted podPress back, but for various reasons the developer has been very busy, had his site forums hacked by spammers, and has otherwise been unable to update his free plugin to work with WordPress 2.6 for several months now. I couldn't wait any longer.
But it turns out the fix is a simple one. The new WordPress feature that seems to be interfering with podPress is post revisions, which track changes to posts. Cool, but I don't use it. The No Revisions plugin turns off that feature, and voila!, podPress works again too.
So I installed No Revisions at both the IHR and Lipgloss sites, deactivated Powerpress at IHR, upgraded to the latest WordPress at Lipgloss (using the great WordPress Automatic Upgrade plugin), and everything seems to be working fine. Page load times have speeded up, simple players are available for all podcast files, and I'm back where I want to be.
If you're a podcaster with similar problems or have been postponing your WordPress upgrade, this solution might work for you too.
Labels: blog, geekery, linkbait, podcast, software, web