Comments on: Be Careful When Upgrading to WordPress 2.2 If You Have the WP-Cache Plugin — Adventures in Backing Up and Restoring WordPress Databases

By: … @ a distance … » UTF-8

… @ a distance … » UTF-8 — Thu, 19 Jun 2008 04:19:35 +0000

[...] in the wp-config.php file. Tried this method, but it didn’t work. Then I read up the idea of converting the SQL in a text editor. It’s kinda manual, but it [...]

By: Lee

Lee — Tue, 11 Sep 2007 03:03:32 +0000

I edited my robots.txt file in Notepad on my girlfriend’s PC when my Mac went out of commission and it borked things—that vexed me pretty well. I can only imagine the pangs of fear and anger screwing up a database with it would cause me.

You’d think UTF-8 would mean UTF-8.

By: videokeman.com

videokeman.com — Thu, 06 Sep 2007 17:43:18 +0000

im have the same wp-cache in my WP setup, Tom’s suggestion worked but i think its better if you have wp-cache to work again.

By: Brian

Brian — Thu, 02 Aug 2007 13:46:16 +0000

I have my backup plugin email me a backup once per week. I really wish I had the option to be sent a backup after each post, but I suppose this schedule accounts for when I make changes to the template as well.

As my dad taught me, “When’s the best time to back up?” “Five minutes ago!”

By: Tom

Tom — Thu, 02 Aug 2007 12:11:04 +0000

Flick,

wow, backups every 6 hours! You are paranoid. Just kidding. Thanks for the recommendation. I agree that an automated backup schedule is ideal.

By: Tom

Tom — Thu, 02 Aug 2007 12:10:13 +0000

David,

If you haven’t solved your problem already, try this:

1. Back up your entire system first.

2. Disable all plugins, and physically delete the wp-cache plugin from your wp-content/plugins directory using an FTP program. (Don’t merely deactivate it.)

3. Download your wp-config file and open it up in Notepad or some equivalent text editor. Remove the line that the wp-cache plugin inserts in it:

define(‘WP_CACHE’, true);

Then re-upload the wp-config file.

4. Upgrade to the latest version of WordPress.

5. Reactivate your plugins (not the wp-cache — you should have removed that one).

You should no longer receive the mutex lock error. At least this process worked for me. The wp-cache plugin is more thoroughly integrated in your blog than you may realize. Let me know if you have success.

By: Flick

Flick — Wed, 01 Aug 2007 15:20:54 +0000

I’ve upgraded one site with no problems to 2.2 but am still taking my time with another one. However, for those wanting ‘cron’ backups, I would really recommend Wp-DB Manager by Lesterchan/Gamerz. It allows you to backup manually but the main feature (imho) is taht it automates backups (including optimising databases) and you can even set it up to have the file (compressed or not) emailed to your email account. You can also adjust the frequency of backups (I’ve set mine to every 6 hours, since ‘daily’ just doesn’t seem to be enough for a paranoid user like myself ^^)

It’s actively supported at the moment, so I think it will be a good alternative to ‘Skippy’s’ plugin.

By: David Dalka

David Dalka — Wed, 01 Aug 2007 13:10:36 +0000

I’m getting this WITHOUT upgrading to 2.2 – anyone have ideas?

Warning: fopen(/home/wlfxymb/public_html/createvalue/wp-content/cache/wp_cache_mutex.lock) [function.fopen]: failed to open stream: Permission denied in /home/wlfxymb/public_html/createvalue/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 96

By: Portal Porto Alegre

Portal Porto Alegre — Sun, 22 Jul 2007 18:33:35 +0000

Well done, great blog and great posts!!!!

By: Tom

Tom — Wed, 13 Jun 2007 02:32:12 +0000

Thanks Aaron. I’m glad to hear it was helpful. Encoding issues can be a big pain.