Localizing wordpress after moving it from one domain name to another? It use to be a pain in the ass to hunt down all the link.. well it still can be. However, these mySQL find and replace commands speed it up a heck of a lot. If your theme is pretty basic, you may be done after running these.
In the commands below, Im going from my old dev address ‘studio2108.com.s52733.gridserver.com’ to my new address ‘studio2108.simplehelix.com’. Remember to back up your database before trying this.. anyway take the 4 lines below, cut them, edit them, and then paste them into phpmyadmin’s SQL tab and your good.
Whats weird is the theme file has hardcoded references to studio2108.com in the header file… im finding and replacing them for now.
update wp_posts set guid = replace(guid,'com.s52733.gridserver.com', 'simplehelix.com');
update wp_posts set post_content = replace(post_content,'com.s52733.gridserver.com', 'simplehelix.com');
update wp_options set option_value = replace(option_value,'com.s52733.gridserver.com', 'simplehelix.com');
update wp_postmeta set meta_value = replace(meta_value, 'com.s52733.gridserver.com', 'simplehelix.com');
Gary 7:00 am on May 10, 2010 Permalink
The techs have to err on the side of caution, additions to the shared environment are rarely allowed. Also things such as git often requires someone at the root level to do the initial setup, not being familiar with git I can’t say if that’s true. Anyway if you’ll open a ticket and reference this, I’ll yum install git on the server you’re on and if that’s all it takes I see no reason we can’t put it on the shared environment, if it requires more than that then most likely it won’t happen.
Mike 8:06 am on May 10, 2010 Permalink
For what it’s worth, we have installed git after further consideration as per Gary’s reply.
Nathan Haskins 12:11 pm on May 10, 2010 Permalink
Thanks a lot guys can’t wait to test it.