As you have noticed, I have upgraded FailWordpress to version 2.7, getting also a new theme in the process. The header image is temporary, until I or someone else gets it fixed. The gallery has also changed: I ditched WPG2 and Gallery 2 because they kept on breaking every time I upgraded Wordpress (of course it’s probably Wordpress’s API and schema instability to blame). Therefore, the gallery had been organized and most likely older posts won’t show images anymore (I’ll get to fix those eventually).

Yesterday I updated _The S.T.E.A.L. Saga _to Wordpress 2.5.1. I thought the upgrade would be painless, but I was wrong. First of all, the auto plugin updater kind of confused between the various plugins, so it marked some as updateable although they weren’t. Then, some plugins (albeit incompatible), disappeared from the plugin list (the fix was downloading a more recent version). The biggest issue was, however, the mangling of my .

I have upgraded this blog to Wordpress 2.5. As a result, there are some functions, such as the image gallery, that have been disabled due to the annoying habit of the Wordpress developers of making core changes in very little time. Please report any problems you find, and notice that although the thumbnails look truncated in the new gallery, the full images are actually displayed correctly. I had to fiddle a bit wit the “new media manager”, not only because it’s in Flash, but because at least on Linux it gives odd results (apparently no one from the WP team bothered to check past Win and OSX?

After some thoughts, I switched dennogumi.org to the dKret theme. Please report any errors you may find. The header is the default image, but it will be changed soon (hint: Melissa, you already know what to do…).

I’ve recently upgraded this blog to Wordpress 2.3. While I’m interested in the new changes this release brings (like tagging support) I question the way the transition to the new version was handled. In particular, I am referring to the (questionable) idea of breaking the database schema three weeks before the release. Given the amount of breakage that brought upon plugins, it should have been announced at the start of the 2.