Just been moving the big blog over. The Wordpress upgrade drill is pretty good. (It works, for one thing). But the shit involved in updating “AN_ropey_theme/plugin” has Got Nothing To Do With A Good Time.
I finally found a 1.5 version of Toni for mama, which seems to put the sidebar in the middle of the page. There’s a ‘Toni Tweaked’ but that’s 1.2 only. Aaargh. I’m going to have to do a theme from scratch for stitch, and I really can’t be bothered.
But for true jaw-dropping clankiness, nothing caps the Flickr gallery plugin 1.2 → 1.5 ‘upgrade’ (the plugin itself looks quite nice once you tweak out a coupla bugs).
I’ve Googled for two hours and the official 1.5 solution is ‘use the 8 month old 1.2 version and apply these horrible hacks to get it working with the new theme model’.
This includes brain deadness like copying gallery.php into your active theme directory.
Pardon? What has a Flickr gallery got to do with theming? I’m going to have to go through this each time I change theme? Not to mention the next upgrade… No. If I want to support multiple layers of buggily patched webapp I’ll stay late at work, thanks.
Poor bastards.
It says something for a language that it’s easier to do this kind of evil hack than update 2 pages of PHP against the new framework.
I’m sorely tempted to try the Typo wordpress migration thing and have done with it.
- I doubt it’ll work, but typo is readable so I have a chance at tweaking it in.
- once I have shoehorned it in, I hopefully get less painful upgrades when a new version comes out
- there’s no rush, I can’t switch to 1.5 until I sort the theme and plugin anyway.
- I know enough Ruby to be dangerous, and I’d enjoy learning more. ‘Life is Too Short to Learn PHP.’
- typos theme framework is sane
- I’ll still need to write my own CSS, but it looks like that’s going to happen either way and it beats the hell out of learning PHP…