Never change a running system; or: WordPress 3.3 *!&%*’#!**!

Seeing a software update the first thoughts that come to mind are security patches, performance improvements and added features. All good reasons to upgrade a system.

WordPress 3.3 was installed quickly and easily without any problems, just as usual.

What are the changes from 3.2 to 3.3? All the main menu items in the left side menu are minimized by default. I don’t like it, but it makes sense for smaller screens, especially when the menu is reduced to the icons.

What else? The new control panel features of the top panel are actually quite useful.

But then the problems begin: the editor has been changed. All the media buttons have been combined into one. Since they weren’t in the way at all quite a superfluous gesture. The real problem is that my flickr photalbum plugin button that is situated next to the media button doesn’t work anymore.

Much worse: qTranslate is broken. A note appears throughout the dashboard:

“The qTranslate editor was deactivated, since it hasn’t been tested with this WordPress version. -blabla about security and then – click here to reactivate.”

Great! Let’s klick the link. What? a non functioning Javascript? ****!

And now? An updated version of the plugin isn’t available. Seem like I’m done blogging in two languages for the time being. I’d really like to know how many other plugins stop working properly after this upgrade. I’m left wondering why it seems impossible for software developers to incorporate backward compatibility into new versions.

Its the same with Firefox but there we at least have the nightly tester tool where the user can re-enable most plugins. THat kind of interim solution would be great for WordPress.

Or maybe give developers two weeks time to update their plugin before enforcing a new standard?

/rant. Let’s see if I need to fall back to 3.2.

 Update: 20.12. qTranslate works again, thanks to an update. I’ll have to replace flickr photoalbum, though.