<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>archGFX &#187; mysql</title>
	<atom:link href="http://archgfx.net/tag/mysql/feed" rel="self" type="application/rss+xml" />
	<link>http://archgfx.net</link>
	<description>Austin web designer - Adam Freetly</description>
	<lastBuildDate>Wed, 28 Sep 2011 13:50:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>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</link>
		<comments>http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain#comments</comments>
		<pubDate>Thu, 10 Apr 2008 12:57:48 +0000</pubDate>
		<dc:creator>adam</dc:creator>
				<category><![CDATA[blogging]]></category>
		<category><![CDATA[migration]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[phpmyadmin]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://archgfx.net/?p=1303</guid>
		<description><![CDATA[When you develop a site on a test server, it's tricky to make sure that none of the old links get carried over to the live site. This tutorial also works if you're moving to a new domain. While using a WordPress export is easier, this method catches everything, which can be important if your [...]]]></description>
			<content:encoded><![CDATA[<p>When you develop a site on a test server, it's tricky to make sure that none of the old links get carried over to the live site.  This tutorial also works if you'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't preserve post ID's</p>
<ol>
<li>Download the exisitng <code>/wp-content/</code> directory (all of it ( some plugins (<a href="http://www.deliciousdays.com/cforms-plugin/">cforms</a>, <a href="http://www.instinct.co.nz/e-commerce/">wp-eCommerce</a>) contain modified or uploaded files)).</li>
<li>Install wordpress on the new domain.  Very few of the settings matter, because they're all going to be overwritten.  Nonetheless, it's easiest to use fantastico or <a href="http://www.simplescripts.com/">Simplescripts</a> to set up the database, and create the basic file structure.</li>
<li>Delete the new <code>/wp-content/</code> folder, and upload the existing /wp-content/ folder.  This step may take a long time, so you can do the next few steps while it's uploading.</li>
<li>Export the old database, using PHPMyAdmin:<br />
<a rel="attachment wp-att-1304" href="http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain/attachment/mysqlexport/"><img class="aligncenter size-medium wp-image-1304" title="mysql export" src="http://archgfx.net/wp-content/uploads/2008/04/mysqlexport-300x246.jpg" alt="Using PHPMyAdmin to Export the MySQL Table" width="300" height="246" /></a></li>
<li>Open the exported <code>*.<acronym title='Structured Query Language'><span class='caps'>SQL</span></acronym></code> file, using a code editor (<a href="http://eclipse.org">Eclipse</a>/<a href="http://aptana.com">Aptana</a>, <a href="http://notepad-plus.sourceforge.net/">Notepad++</a>, or (god forbid) Dreamweaver), and find and replace the old domain name with the new one.<br />
<a rel="attachment wp-att-1305" href="http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain/attachment/mysqlreplace/"><img class="aligncenter size-medium wp-image-1305" title="mysql replace" src="http://archgfx.net/wp-content/uploads/2008/04/mysqlreplace-299x289.jpg" alt="Find and Replace in Aptana" width="299" height="289" /></a></li>
<li>After step 4 has completely finished (so that all of the plugins and themes exist before WordPress attempts to use them), use PHPMyAdmin on the new host to delete the newly created database tables<br />
<a rel="attachment wp-att-1306" href="http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain/attachment/mysqldrop/"><img class="aligncenter size-medium wp-image-1306" title="mysql drop" src="http://archgfx.net/wp-content/uploads/2008/04/mysqldrop-300x200.jpg" alt="Drop the tables in PHPMyAdmin" width="300" height="200" /></a></li>
<li>... and import the new ones.<br />
<a rel="attachment wp-att-1307" href="http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain/attachment/mysqlimport/"><img class="aligncenter size-medium wp-image-1307" title="mysql import" src="http://archgfx.net/wp-content/uploads/2008/04/mysqlimport-300x168.jpg" alt="Import the Modified file using PHPMyAdmin" width="300" height="168" /></a></li>
<li>On the existing install, set the blog address to the new <acronym title='Uniform Resource Locator'><span class='caps'>URL</span></acronym>.  this ensures that any google juice that the development server may have picked up will be transfered to the new domain (this isn't necessary if the development server doesn't face the internet).<br />
<a rel="attachment wp-att-1308" href="http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain/attachment/blogurl/"><img class="aligncenter size-medium wp-image-1308" title="blog url" src="http://archgfx.net/wp-content/uploads/2008/04/blogurl-300x98.jpg" alt="Changing the Blog Address" width="300" height="98" /></a></li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://archgfx.net/blog/2008/geek/blogging/migrating-a-wordpress-install-to-a-new-domain/feed</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
	</channel>
</rss>

