On January 22nd, the Automattic crew unleashed WordPress 2.1 on the world, thereby wrecking (ok, causing minor problems with) a bundle of themes in the process. Sadly, Cutline was among the ranks of the afflicted themes, but only for reasons that were not unexpected.
Naturally, I can’t just leave you with a theme that is anything less than fully functional, so to solve this problem, I’m going to release a newer, hotter, better version of Cutline within the next few hours. In fact, by the time you finish reading this post, it’ll probably already be here.
Until then, it’s time to think about making this important upgrade, and I’d like to take this time to examine the following:
- Potential issues with the WordPress 2.1 upgrade
- How this upgrade affects Cutline
- What you can do to ensure that your theme is performing at optimum levels for whatever version of WordPress you choose to run.
WordPress 2.1 Upgrade Issues
For those of you who haven’t already upgraded to WordPress 2.1, there are a few important things that you need to know before you make the switch. I’ve had a few days to install 2.1 on a couple of different servers and tinker accordingly, and I’ve come across a couple of red flags that I’d like to share here.
First, not all Web hosting packages are robust enough to support WordPress 2.1. I have a shared server with MediaTemple that I purchased in late 2005, and when I tried to upgrade WordPress, I was unable to do so because the old shared server package does not support mySQL 4.0, which is required by 2.1 in order to take advantage of some new database upgrades and features.
That same shared server package from MediaTemple was extremely popular among bloggers up until the release of their new GridServer, so it’s quite possible that you might find yourself in the same boat as I was with my test server. If that’s the case, then you are left with a couple of options:
- Upgrade to the new GridServer (for more money).
- Switch to MidPhase (for less money), gain more control over your site’s statistics, and get a free domain name. This site runs on a MidPhase server, and I was able to upgrade to WordPress 2.1 without a hitch.
Second, it is quite likely that some of your plugins will fail after upgrading — unless, of course, you’ve already taken the measures to download newer versions that are compatible with WordPress 2.1. With that said, I suppose the moral of this paragraph is simply to check your plugins.
How WordPress 2.1 Affects Cutline
All along, I’ve said that Cutline was a robust, simple, and flexible theme. If I had been telling you the truth, then why did your blogrolls break when you upgraded to WordPress 2.1?
The reason for this is the fact that up until version 2.1, WordPress auto-generated inconsistent blogroll code. Instead of applying a common class to all link lists, WordPress actually applied unique IDs to each separate blogroll category. This inefficient code resulted in an infinite number of XHTML possibilities for the resulting blogroll markup, and as a result, I had to choose how many individual categories I would support in the CSS.
As of WordPress 2.1, my adaptive CSS for the blogroll is obsolete, and this is precisely why your blogroll is “broken.” So what’s the fix? The new version of Cutline, which is coming soon. Like, maybe even now — check the sidebar to be sure.
Update: Here it is!
Another way that WordPress 2.1 affects Cutline is through the discontinued use of some deprecated template tags. It’s nothing too major, but there’s a good chance that your categories may display awkwardly (or not at all) on your Archives or Sitemap pages. No worries, though, as I’ve cleaned this up on the new version of the theme.
Legacy Support for Cutline
But wait, I won’t be able to upgrade to 2.1 anytime soon, but I still want to use the theme! What can I do?
Easy, tiger. I know you’re out there, and I’ve got you covered.
If you’re running WordPress 2.0.7 or older, then use these links to get your blog set up and working like a champ.
- Download Cutline 1.03
- Implement random header images by checking out this post.
- If you don’t already have it, you can snag the Cutline 1.03 sitemap here.