I'm attempting to migrate a wordpress website to a different server, that is on mediatemple.
Inside migration guide, it indicates upgrading the website preview/pathways towards the IP from the server.
It provides a SQL query to operate in phpMyAdmin that is:
UPDATE `dbname`.`wp_options` SET `option_value` = 'http://xxx.xxx.xxx.xxx' WHERE `wp_options`.`option_id` =1 AND `wp_options`.`blog_id` =0 AND CONVERT( `wp_options`.`option_name` USING utf8 ) = 'siteurl' LIMIT 1 ;
But can't get results because it reviews a mistake after i run it.
This is actually the up-to-date query put with my particulars:
UPDATE `db87924`.`db87924_rockhaq` SET `option_value` = 'http://64.207.145.39' WHERE `wp_options`.`option_id` =1 AND `db87924_rockhaq`.`blog_id` =0 AND CONVERT( `wp_options`.`option_name` USING utf8 ) = 'siteurl' LIMIT 1 ;
I am speculating that 'option_value', 'wp_options', 'option_id' and 'option_name' have to be changed with something but have no clue what and should not find anymore information on it.
If anybody has any ideas, that might be great!
Thanks
wordpress-config.php may also has some hardcoded pathways which have to be transformed.
http://codex.wordpress.org/Editing_wp-config.php#WordPress_address_.28URL.29
Always backup the database just in case something goes awry. :D
This is actually the query I'd use emigrate the Wordpress install and it has labored for me personally to date (may be different for you personally):
UPDATE wp_options SET option_value='http://64.207.145.39' WHERE option_name='siteurl';
UPDATE wp_options SET option_value='http://64.207.145.39' WHERE option_name='home';
However, in case your Wordpress install hosts a lot more than 1 blog, i quickly would update the query to:
UPDATE wp_options SET option_value='http://64.207.145.39' WHERE option_name='siteurl' AND blog_id=0;
UPDATE wp_options SET option_value='http://64.207.145.39' WHERE option_name='home' AND blog_id=0;
These alter the pathways/links in Wordpress (in my opinion, both configurations have to be transformed: home and siteurl).
If the works, you'd most likely have to run the query again once the DNS is moved.