Blog problems

I guess it’s a good thing that if folks are having problems, they’re telling me about them …  Better to have no problems at all, of course, but complaints are better than a broken site that folks don’t bother reporting, right?

I am having a few problems come in since the MT4 install.

1. The edit buttons in the comments (for this blog — I never implemented it elsewhere) are missing.  I think I know how to fix that (copy the old mt.js over to the blog root and uncomment it), but in case that breaks, there are other ways to do it.  If nothing else, you can always put a link in plaintext in the comment, and it will automagically turn into a link.  Ugly, but effective.  I think that there are some other input formats for comments that are now supported, too (Textile, for example), but I’m not *sure* …
2. TypeKey stuff is dodgy.  I don’t know how many folks actually use that here still (as it’s optional), but I’ve had at least one report on this blog (from Les) that he had to sign off from TypeKey in order to comment.  I also ran into a problem on my in-laws’ computer that wouldn’t allow them to sign off (or, rather, it did, but it didn’t show the sign-off, but it didn’t let them input the required fields for the comment manually).  This is one I’m reluctant to touch too much because the code is a real mess.  I may just take out TypeKey for this blog.  This might also be affecting WIST.  Pending.
3. Some comments seem to be just failing.  I’m not 100% sure of this, though.  Watching.
4. MT changed the headers for notification e-mails I get from the various blogs here, so I’m now getting everything showing up in my mail rather than just the exceptions (Moderations).  Investigating.
5. Found at least one set of stuff over on the WIST side of things that’s thrown by the difference between where the code resides and the WIST domain.  Poking into that.