Just finished upgrading this site. The upgrade went well on my test server and fortunately it also went well here. There was some odd issue with phpMyAdmin's backup though. Everything is UTF-8, nevertheless the dump started with the following line:
CREATE DATABASE `foo` DEFAULT CHARACTER SET latin1 COLLATE latin1_swedish_ci;
Swedish? Well, "latin1" was already totally off, but that? Uhm.
Well, it was good for a laugh. Fortunately the dump itself was still UTF-8 encoded and everything was fine - after getting rid of that really weird line, that is.
Did you ever wonder what my first post was all about? Well, by now you might have guessed it. It's a quick method to check the encoding after a rollback. If you don't have a specific test page, you may not notice that something went wrong. If you're unlucky, you'll notice it weeks or even months later and there will be lots of new content. With a different encoding, that is. Once the encodings are mixed all over the place it gets really nasty. So, do yourself a favor and check the encoding right after a rollback.
Oh and there is a small glitch over in Drupal's HTML Corrector. It breaks HTML comments (it escapes the '<' character of the start tag). The description of the Full HTML input format doesn't mention the HTML Corrector though. Well, I only needed HTML comments for that Adsense block. So, switching to the PHP code input format over there wasn't much of an issue.
I also ported SHJSFilter over beforehand. It was surprisingly pain-free. If nothing pops up, I'll release the new version tomorrow. I'm not really sure if there are actually any other sites which use it though.