Always check your plugins

I wound up losing about 2 hours of my day today (yes, New Year’s Day) thanks to some problems with the latest version of the PodPress plug in. While making some changes on the Plane Crazy Down Under site, I noticed that a Plugin was ready for update. I dutifully ran the update process and upgraded to the latest PodPress version (8.8.2). All seemed OK and I went about my day.


An hour or so later, I received an SMS from Steve, my partner in PCDU saying there was a problem with the podcast’s feed. Yup, the feed’s text was there but the mp3 files couldn’t download.

I ran the feed through the Feed Validator and it confirmed that the mp3 file had to have a full path, not a relative one. Damn – looks like the updated PodPress is to blame.

With a bit of effort I picked up the previous version of the plugin, deleted the current version from the site and loaded the previous version. NOTE: WordPress makes it easy to load updated plugins (and themes, and WordPress versions – for which we’re all extremely greatful :) but there’s no easy way to roll back to a previous version. Oh well.

Once rolled back, I then spent a while getting the FeedBurner feed sorted out (took a ping to get it to refresh) and did the same (ping) for iTunes. After that it was just a matter of “Check for Updates” on the podcast in iTunes and everything started working fine again.


The lesson learned: Don’t upgrade to the latest version of a plugin without checking to see a) how long it’s been around and b) whether anyone’s hit any snags with it yet. Also a good idea to not upgrade when you’d rather be spending the day chilling out & relaxing :)