Ya, the key is updating the meta option for url in the database to fix the log in problem.
I’d have to say that the “moving WordPress” page doesn’t quite cleanly solve the dev to production problem yet…
A few things need to be built:
1. Something that translates serialized data from dev to production.
2. Something that let’s WordPress know if it’s on dev or production. Maybe a yaml file gets read, since that’s what the cool kids do. 😛
3. Something that let’s you make sure you don’t accidentally erase blog posts on production and just let’s you transfer the data you need. Right now, it’s pretty easy to blow data in production. :-\
The serialized data will be an issue. It’s not enough to just replace my-dev-site.com with my-production-site.com . You need to change the numbers that store the string length in the serialized data.