<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Migrating a WordPress Install to a New Domain</title>
	<atom:link href="http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain/feed" rel="self" type="application/rss+xml" />
	<link>http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain</link>
	<description>Austin web designer - Adam Freetly</description>
	<pubDate>Thu, 04 Dec 2008 20:01:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Andy Howard</title>
		<link>http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain#comment-32096</link>
		<dc:creator>Andy Howard</dc:creator>
		<pubDate>Wed, 13 Aug 2008 14:08:05 +0000</pubDate>
		<guid isPermaLink="false">http://archgfx.net/?p=1303#comment-32096</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>Awesome guide, just what I&#8217;ve been looking for. I&#8217;ve found migrations a little tricky in the past, and this will really help me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: adam</title>
		<link>http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain#comment-30816</link>
		<dc:creator>adam</dc:creator>
		<pubDate>Fri, 25 Apr 2008 21:21:13 +0000</pubDate>
		<guid isPermaLink="false">http://archgfx.net/?p=1303#comment-30816</guid>
		<description>@HSO -
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;code&gt;'dev.site.local/temp&lt;/code&gt;
with
&lt;code&gt;'example.com&lt;/code&gt;

And yes, it's very important to make sure you have the same database prefix.</description>
		<content:encoded><![CDATA[<p>@HSO -<br />
interesting, i&#8217;ve never seen a setup that didn&#8217;t include the <a href="http://" rel="nofollow">http://</a> prefix.  The reason I included the <a href="http://" rel="nofollow">http://</a> is to make sure that there aren&#8217;t www&#8217;s left over.  if you&#8217;re find/replacing without the <a href="http://" >http://</a>, you should replace<br />
<code>'dev.site.local/temp</code><br />
with<br />
<code>'example.com</code></p>
<p>And yes, it&#8217;s very important to make sure you have the same database prefix.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hso</title>
		<link>http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain#comment-30815</link>
		<dc:creator>hso</dc:creator>
		<pubDate>Fri, 25 Apr 2008 19:42:23 +0000</pubDate>
		<guid isPermaLink="false">http://archgfx.net/?p=1303#comment-30815</guid>
		<description>In some instances, the SQL data will not contain the http prefix, so it's better to just find and replace without the http://

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.</description>
		<content:encoded><![CDATA[<p>In some instances, the <acronym title='Structured Query Language'><span class='caps'>SQL</span></acronym> data will not contain the http prefix, so it&#8217;s better to just find and replace without the <a href="http://" >http://</a></p>
<p>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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: richard</title>
		<link>http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain#comment-30741</link>
		<dc:creator>richard</dc:creator>
		<pubDate>Fri, 11 Apr 2008 01:46:58 +0000</pubDate>
		<guid isPermaLink="false">http://archgfx.net/?p=1303#comment-30741</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>Thanks for putting this up. I&#8217;m not planning on moving anytime soon, but I&#8217;ve bookmarked it. Who knows what the future will bring.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How to migrate a wordpress blog to your own domain &#171; one cool site: wordpress blogging tips</title>
		<link>http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain#comment-30739</link>
		<dc:creator>How to migrate a wordpress blog to your own domain &#171; one cool site: wordpress blogging tips</dc:creator>
		<pubDate>Thu, 10 Apr 2008 20:20:43 +0000</pubDate>
		<guid isPermaLink="false">http://archgfx.net/?p=1303#comment-30739</guid>
		<description>[...] How to migrate a wordpress blog to your own&#160;domain  I was interested to find this illustrated blogging tips tutorial which describes an alternative method for migrating a wordpress blog to a domain.  When you develop a site on a test server, it&#8217;s tricky to make sure that none of the old links get carried over to the live site. This tutorial also works if you&#8217;re moving to a new domain. While using a WordPress export is easier, this method catches everything, which can be important if your theme links to specific pages, since WordPress exports don&#8217;t preserve post ID&#8217;s &#8230; -&#62; Read the whole article.  [...]</description>
		<content:encoded><![CDATA[<p>[...] How to migrate a wordpress blog to your own&nbsp;domain  I was interested to find this illustrated blogging tips tutorial which describes an alternative method for migrating a wordpress blog to a domain.  When you develop a site on a test server, it&#8217;s tricky to make sure that none of the old links get carried over to the live site. This tutorial also works if you&#8217;re moving to a new domain. While using a WordPress export is easier, this method catches everything, which can be important if your theme links to specific pages, since WordPress exports don&#8217;t preserve post ID&#8217;s &#8230; -&gt; Read the whole article.  [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
