<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: MT import update</title>
	<atom:link href="http://wordpress.org/news/2003/06/mt-import-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://wordpress.org/news/2003/06/mt-import-update/</link>
	<description>WordPress News</description>
	<lastBuildDate>Fri, 22 Jan 2010 06:50:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-RC1</generator>
	<item>
		<title>By: Jennifer</title>
		<link>http://wordpress.org/news/2003/06/mt-import-update/#comment-185</link>
		<dc:creator>Jennifer</dc:creator>
		<pubDate>Tue, 29 Jul 2003 08:32:09 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2003/06/mt-import-update/#comment-185</guid>
		<description>I&#039;d love to try out WP, but I need the MT importer first........</description>
		<content:encoded><![CDATA[<p>I&#8217;d love to try out WP, but I need the MT importer first&#8230;&#8230;..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KC</title>
		<link>http://wordpress.org/news/2003/06/mt-import-update/#comment-184</link>
		<dc:creator>KC</dc:creator>
		<pubDate>Fri, 04 Jul 2003 16:52:52 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2003/06/mt-import-update/#comment-184</guid>
		<description>how is this import tool develpoment going? it&#039;s the only thing blocking me from switching right now!</description>
		<content:encoded><![CDATA[<p>how is this import tool develpoment going? it&#8217;s the only thing blocking me from switching right now!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Williamson</title>
		<link>http://wordpress.org/news/2003/06/mt-import-update/#comment-183</link>
		<dc:creator>Bill Williamson</dc:creator>
		<pubDate>Fri, 13 Jun 2003 04:12:22 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2003/06/mt-import-update/#comment-183</guid>
		<description>I agree with rev jim... use the export feature of MT for imports.  Then sql doesn&#039;t even come into it, it&#039;s simply a matter of parsing a flat file.</description>
		<content:encoded><![CDATA[<p>I agree with rev jim&#8230; use the export feature of MT for imports.  Then sql doesn&#8217;t even come into it, it&#8217;s simply a matter of parsing a flat file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reverend Jim</title>
		<link>http://wordpress.org/news/2003/06/mt-import-update/#comment-182</link>
		<dc:creator>Reverend Jim</dc:creator>
		<pubDate>Tue, 10 Jun 2003 20:20:39 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2003/06/mt-import-update/#comment-182</guid>
		<description>I&#039;m glad you decided to provide an MT Import. I feel that is the best way to ensure you get lots of users/testers quickly. Please, if at all possible, create a method to, at least in most cases, provide redirects from old MT urls to new WP urls. At the very least, provide a little mod_rewrite HOWTO in the readme for the import tool. Broken links are bad things.

As far as the import goes, Pulling in the MT export format may be your best bet even with the MySQL version of MT. This way, if users are doing something crazy that you don&#039;t expect, as long as they can shove it into the MT export format, your import tool will be able to handle it. This also means that even OOOOOOOLD versions of MT will be able to export its data.</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad you decided to provide an MT Import. I feel that is the best way to ensure you get lots of users/testers quickly. Please, if at all possible, create a method to, at least in most cases, provide redirects from old MT urls to new WP urls. At the very least, provide a little mod_rewrite HOWTO in the readme for the import tool. Broken links are bad things.</p>
<p>As far as the import goes, Pulling in the MT export format may be your best bet even with the MySQL version of MT. This way, if users are doing something crazy that you don&#8217;t expect, as long as they can shove it into the MT export format, your import tool will be able to handle it. This also means that even OOOOOOOLD versions of MT will be able to export its data.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

