<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Austin Web Designer - Adam Freetly - Latest Comments in Migrating a WordPress Install to a New Domain</title><link>http://archgfx.disqus.com/</link><description>Web Design, Wordpress Themes, Music, and Randomness</description><atom:link href="https://archgfx.disqus.com/migrating_a_wordpress_install_to_a_new_domain/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 13 Aug 2008 10:08:05 -0000</lastBuildDate><item><title>Re: Migrating a WordPress Install to a New Domain</title><link>http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain#comment-1517798</link><description>&lt;p&gt;Awesome guide, just what I've been looking for. I've found migrations a little tricky in the past, and this will really help me.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andy Howard</dc:creator><pubDate>Wed, 13 Aug 2008 10:08:05 -0000</pubDate></item><item><title>Re: Migrating a WordPress Install to a New Domain</title><link>http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain#comment-1517796</link><description>&lt;p&gt;@HSO -&lt;br&gt;interesting, i've never seen a setup that didn't include the http:// prefix.  The reason I included the http:// is to make sure that there aren't www's left over.  if you're find/replacing without the http://, you should replace &lt;br&gt;&lt;code&gt;'dev.site.local/temp&lt;/code&gt;&lt;br&gt;with&lt;br&gt;&lt;code&gt;'example.com&lt;/code&gt;&lt;/p&gt;&lt;p&gt;And yes, it's very important to make sure you have the same database prefix.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">sunburntkamel</dc:creator><pubDate>Fri, 25 Apr 2008 17:21:13 -0000</pubDate></item><item><title>Re: Migrating a WordPress Install to a New Domain</title><link>http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain#comment-1517795</link><description>&lt;p&gt;In some instances, the SQL data will not contain the http prefix, so it's better to just find and replace without the http://&lt;/p&gt;&lt;p&gt;Also, it is imperative that the prefix used while creating the database both on your local server/old site and online/new site are the same. WordPress by default uses wp_ as the prefix (in wp-config.php), but if your any reason you changed it, you should use that very prefix on the new install. Adam, correct me if I am off here.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">hso</dc:creator><pubDate>Fri, 25 Apr 2008 15:42:23 -0000</pubDate></item><item><title>Re: Migrating a WordPress Install to a New Domain</title><link>http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain#comment-1517794</link><description>&lt;p&gt;Thanks for putting this up. I'm not planning on moving anytime soon, but I've bookmarked it. Who knows what the future will bring.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">richard</dc:creator><pubDate>Thu, 10 Apr 2008 21:46:58 -0000</pubDate></item></channel></rss>