I'm running 3.21, so now that 4.21 is out I've reached my goal of always being one full version behind.

One reason I am loath to install new stuff is simply that I have a design that I like, that my users have hailed as, if not wondrous, certainly Not Awful, and I always worry that I won't be able to keep that look - especially since the templates I'm using are based on (gasp!) 2.21 and are now in their seventh year.

So I anticipate whole boatloads of Fail should I move up into the 4.x range. Perusal of this section suggests that I'm going to have stylesheet issues, though I'm thinking that if my templates actually still work, I should be able to reimplant my old stylesheet and be done with it.

And if you're asking "Why upgrade if you're happy with what you have?" the answer is this: right now, for some reason, it takes six whole minutes to publish a new post in 3.21. (I have just over 4000 posts in this database and about ten thousand comments.) The MT interface itself moves with stirring swiftness, suggesting that it's not an issue with the MySQL server. I have been unable to figure out where the delays are coming in, tech support at the host is mystified, and eventually, I assume, they're going to say "Why don't you just upgrade the application?"

I await the wisdom of the community.

You will only have style sheet issues if you either a) refresh your blog templates to v4 but try to use you own style sheet or b) try to use a v4 style sheet with your custom templates.

What I did for one site was set up a local test server running the 3.21 site and did the upgrade to see if anything had gone wrong, it had not but I had already decided to do a complete refresh.

Well, I failed. Miserably. Not only does 4.21 error out with a 500, I can't go back to 3.21.

Obviously it was never meant to be.

Here's the deal, or at least one of them:

mt.check.cgi says:
# Current working directory: /home/.eve/dbphobe/dustbury.com/mt

This is wrong. This hasn't been the working directory for over a year.

Where can I edit something to change this so that mt-upgrade.cgi (or even mt.cgi) will work?

How did you do the upgrade?

Current working directory is calculated from where the script is running from, it is not a config setting.

Right over the top of the old one, which proved to be a mistake; I eventually had to abandon it and create a new MT 4 directory. A couple of renames, and we're in business, sort of, though this still makes no sense to me: evidently that long-ago directory was written to some obscure file I don't know about, and MT wouldn't let go of it until it was faced with a brand-new set of files and look for the darn thing itself.

In the previous install did you have to edit bootstrap.pm? (although that still would not make sense as it would have been over written)

I did not. (And it still makes no sense.)