[wp-hackers] siteurl and home should not be in the mysql database

Paul Menard codehooligans at codehooligans.com
Sun Jun 17 14:21:09 GMT 2007

On Jun 17, 2007, at 1:50 AM, Gali wrote:

> Thanks for all you SQL tricks about changing the options after an  
> import.
> That's NOT what I was looking for (and NOT what you should be  
> doing, btw).
> On a SQL export, I want to move the content, not the meta data.

If you are moving the content (wp_content) you are best to also move  
the wp_postmeta. IF changes made to the content that affects the  
template, attachments, custom fields they are stored in the  
wp_postmeta table. Otherwise your two systems are out of sync.

> Computer Guru showed the best solution, by putting the option in a
> file (like OsCommerce - ok, not a coding reference :D)

I'm interested in this approach. Is this actually documented  
somewhere?? Is this a define() setting or just WP_HOME="http://....'.  
I did a search on the two keywords WP_HOME and WP_SITEURL in the WP  
codebase and found nothing.

I'm interested in what is affected as far as the actual records of  
the wp_posts table namely the guid field. So when the DB records are  
imported and someone hits the HOME URL are the values for the guid  
field converted to the WP_HOME URL defined in the wp-config.php file?

More information about the wp-hackers mailing list