WP 2.0.6 Errors after Upgrading

Oh, you have ’em in IE7 too, it just must not show them.

Now, you forgot to share those errors with us… without seeing them, not much we can do but cluck our tongues and offer sympathy. ??

I’d like to update. I’m getting more database connection errors in both Firefox and IE7. However, it’s very weird how I’m getting them. I can log into wp-admin, go to Write, go to Manage. I clicked on Edit for a post under Manage. The post shows up in the editor, all the categories are there. Under the Save button, there’s a bunch of errors about connecting to the database, same as with the Post Preview section.

Here’s some of the errors (username and partial paths removed for safety):

WordPress database error: [Can’t connect to local MySQL server through socket ‘/var/lib/mysql/mysql.sock’ (111)]
SELECT * FROM wp_users WHERE user_login = ‘<user>’

WordPress database error: [Can’t connect to local MySQL server through socket ‘/var/lib/mysql/mysql.sock’ (111)]
SELECT * FROM wp_users WHERE user_login = ‘<user>’

Warning: Cannot modify header information – headers already sent by (output started at /<path>/wp-includes/wp-db.php:104) in /<path>/wp-includes/pluggable-functions.php on line 270

I need to get this fixed ASAP.

Thanks,
Matt

Can’t connect to local MySQL server through socket ‘/var/lib/mysql/mysql.sock’ (111)

That’s MySQL pitching a snit. You want to share that error message with your host.

What happens when all plugins are deactivated, then activated and tested one by one in order to find the culprit?
Did you try to connect to https://www.loot-ninja.com/wp-admin/upgrade.php ?

I ran the upgrade a couple times and it said it was fine. I’m going through now and redoing all the files and doing the upgrade again. All plugins are deactivated and I’m uploading files now. I’ll see if that makes any difference.

I’ll also get in touch with my host about the mysql errors.

Ok so after doing the upgrade again, I can’t even access wp-admin. I get an error screen saying it get access the database connection. I read somewhere that I should try manually changing the database user password? Or does it seem like there’s an error with the database server?

Only thing I did different with this upgrade was delete wp-content/cache, as per the detailed upgrade instructions on this site. Could that have done it?

I’m going to guess that the cache was from an earlier version of WordPress.

It also helps, when you’re uploading the 2.0.6 files, to delete the earlier versions (except for the ones listed in the Codex upgrade page). I’d never experienced it before yesterday, but some files may not get properly overwritten when FTPing, and thus the suggestion to delete the earlier files.

I deleted everything except what was stated in the detailed upgrade instructions, and did everything like it said. I’m baffled. Never had any problems with upgrades.

Odd. If you’ve got your original database backup, I’d simply dump the database tables and import the backup, then upload the old WP files so that your blog is restored. Then start the upgrade again.

Stuff happens. One blinks. And things can go wrong. ??

I may have to do that. I just noticed a new thing: Sometimes I’ll click something and get a full page of errors, all starting with:

WordPress database error: [Can’t connect to local MySQL server through socket ‘/var/lib/mysql/mysql.sock’ (111)]

But at the bottom of the page, I get:

Your database is out-of-date. Please upgrade.

Does this mean there’s a problem with my database? Or is there a problem with the server?

My webhost, afer denying a problem twice, FINALLY admitted it was their issue.