SQL for migrating a WordPress DB between domains

nick — Wed, 05 May 2010 15:59:42 +0000

When working locally on a wordpress site there’s 2 references to the local server address stored in wordpress’ ‘wp_options’ table. These handy bits of sql will update the DB when you have imported to the live server:

/* update wordpress sql */
UPDATE `wp_options` SET `option_id`='1', `blog_id`='0', `option_name`='siteurl', `option_value`='[NEW DOMAIN NAME HERE]', `autoload`='yes' WHERE `option_id` = '1' AND `blog_id` = '0' AND `option_name` = 'siteurl';
 
UPDATE `wp_options` SET `option_id`='39', `blog_id`='0', `option_name`='home', `option_value`='[NEW DOMAIN NAME HERE]', `autoload`='yes' WHERE `option_id` = '39' AND `blog_id` = '0' AND `option_name` = 'home';

WordPress mu and mamp pro

nick — Wed, 21 Jan 2009 19:25:21 +0000

If your trying to get WordPress mu working on your local testing serving running Mamp Pro; you might get an unexpected port number warning. To get round this in Mamp Pro click on ‘Server’ button. Within the ‘General’ tab click ‘Default ports’ button for the Apache ports. This will change the port number to 80 – the standard port for http serving.

By making this small adjustment your test domain urls will now look like test-domain.test/ instead of test-domain.test:8888/.

Make sure when you set up a new test domain always use a .test, .local etc domain extension. Basically not the live site domain – no end of problems will start for you! Also, I have the ‘Local name resolution’ checked under the domain name.

seventy6 » wordpress

SQL for migrating a WordPress DB between domains

WordPress mu and mamp pro