Well, that’s unfortunate

As I’ve said before, I’ve tried to keep a local version of my site mirrored to my online version. This isn’t unusual for a lot of developers; it helps to stage your site, it allows you to make mistakes with little impact on the outside world and it allows you to be productive away from an Internet connection.

I’ve been fairly successful at doing this with WordPress 2.x. The new version seems to be a somewhat different story. My typical method of duplication is to:

1. Copy the site folder from on location to another
2. Copy the MySQL database with the following changes:
   1. Change references from www to my local MAMP server (www.wellys.com to wellys.com:8888)
   2. Change file location references as well (/Home/lkoepsel to /Users/Shared)
   3. Change the wp-config file for the proper local information

Not this time with 3.0:

1. The Header didn’t change to my custom header
2. The menus didn’t change to my custom menus

So far (cross fingers) those two items seem to be the only issues. Mmmm. I hate it when this happens.

UPDATE:

1. The image for my header was in my media uploads folder but it wasn’t available to use for the twentyten theme (the twentyten theme only pulls images from your system and not from the media library). So I had to delete the image from my media library then reload it in the theme loader… sigh.
2. The menus were setup but not enabled. I simply had to choose the menu in the theme menu settings then save menus and I was up to speed. That was nice.

UPDATE (again):

1. In the past, I typically just reloaded the MySQL tables to ensure the two blogs were identical, this isn’t as easy. Instead, I have the same two issues happening again AND I’m starting to get pingbacks from my own site. This is getting to be a nasty mess.