<?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: Permalink Issues When Moving from Typepad to WordPress</title>
	<atom:link href="http://www.devlounge.net/code/permalink-issues-when-moving-from-typepad-to-wordpress/feed" rel="self" type="application/rss+xml" />
	<link>http://www.devlounge.net/code/permalink-issues-when-moving-from-typepad-to-wordpress</link>
	<description>Design, Develop, and Grow</description>
	<lastBuildDate>Wed, 08 Feb 2012 09:03:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Alec</title>
		<link>http://www.devlounge.net/code/permalink-issues-when-moving-from-typepad-to-wordpress/comment-page-1#comment-180046</link>
		<dc:creator>Alec</dc:creator>
		<pubDate>Fri, 17 Jul 2009 21:34:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/articles/php/permalink-issues-when-moving-from-typepad-to-wordpress#comment-180046</guid>
		<description>Cool methodology David.

For us (and we do a lot of Typepad to Wordpress moves) we found the best way to do it is to grab the actual Typepad URLs as fixed fields and import them with the posts themselves (sometimes you change the URL in Typepad as well and as Stephane pointed out, SixApart did bounce the syntax around).

To do that, you need to use upgrade to pro and use custom templates for the export. Downloadable templates in our &lt;a href=&quot;http://foliovision.com/2008/11/17/typepad-to-wordpress/&quot; rel=&quot;nofollow&quot;&gt;Typepad to Wordpress guide&lt;/a&gt;.

The sad thing is SixApart deliberately cripples Typepad export as I found when I interviewed &lt;a href=&quot;http://foliovision.com/2009/05/12/typepad-export-options/&quot; rel=&quot;nofollow&quot;&gt;Anil Dash&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Cool methodology David.</p>
<p>For us (and we do a lot of Typepad to WordPress moves) we found the best way to do it is to grab the actual Typepad URLs as fixed fields and import them with the posts themselves (sometimes you change the URL in Typepad as well and as Stephane pointed out, SixApart did bounce the syntax around).</p>
<p>To do that, you need to use upgrade to pro and use custom templates for the export. Downloadable templates in our <a href="http://foliovision.com/2008/11/17/typepad-to-wordpress/" rel="nofollow">Typepad to WordPress guide</a>.</p>
<p>The sad thing is SixApart deliberately cripples Typepad export as I found when I interviewed <a href="http://foliovision.com/2009/05/12/typepad-export-options/" rel="nofollow">Anil Dash</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephane</title>
		<link>http://www.devlounge.net/code/permalink-issues-when-moving-from-typepad-to-wordpress/comment-page-1#comment-141947</link>
		<dc:creator>Stephane</dc:creator>
		<pubDate>Wed, 05 Mar 2008 23:07:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/articles/php/permalink-issues-when-moving-from-typepad-to-wordpress#comment-141947</guid>
		<description>One other thing... is the images. Moving the images out of Typepad and in Wordpress is a challenge as well!</description>
		<content:encoded><![CDATA[<p>One other thing&#8230; is the images. Moving the images out of Typepad and in WordPress is a challenge as well!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephane</title>
		<link>http://www.devlounge.net/code/permalink-issues-when-moving-from-typepad-to-wordpress/comment-page-1#comment-141946</link>
		<dc:creator>Stephane</dc:creator>
		<pubDate>Wed, 05 Mar 2008 23:04:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/articles/php/permalink-issues-when-moving-from-typepad-to-wordpress#comment-141946</guid>
		<description>Nice find David!

One thing though...Prior to June 2007, Typepad was using &quot;underscore&quot; as a word delimiter. That has been changed to &quot;-&quot;, but all posts prior to June 2007 will still have &quot;_&quot;...

Any thoughts on how this can be solved? Some sort of find and replace?</description>
		<content:encoded><![CDATA[<p>Nice find David!</p>
<p>One thing though&#8230;Prior to June 2007, Typepad was using &#8220;underscore&#8221; as a word delimiter. That has been changed to &#8220;-&#8221;, but all posts prior to June 2007 will still have &#8220;_&#8221;&#8230;</p>
<p>Any thoughts on how this can be solved? Some sort of find and replace?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

