<?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: Wordpress 2.7 breaks the Redirection plug-in?</title>
	<atom:link href="http://www.tdaxp.com/archive/2009/01/05/wordpress-27-breaks-the-redirection-plug-in.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.tdaxp.com/archive/2009/01/05/wordpress-27-breaks-the-redirection-plug-in.html</link>
	<description>All of us against the machine</description>
	<lastBuildDate>Sat, 20 Mar 2010 03:18:56 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Posts about Wordpress 2.7 as of January 5, 2009 &#124; The Lessnau Lounge</title>
		<link>http://www.tdaxp.com/archive/2009/01/05/wordpress-27-breaks-the-redirection-plug-in.html/comment-page-1#comment-211915</link>
		<dc:creator>Posts about Wordpress 2.7 as of January 5, 2009 &#124; The Lessnau Lounge</dc:creator>
		<pubDate>Tue, 06 Jan 2009 19:34:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.tdaxp.com/?p=6686#comment-211915</guid>
		<description>[...] , and sometimes do not seem to justify the hassle involved in doing the upgraded. But version 2.7   Wordpress 2.7 breaks the Redirection plug-in? - tdaxp.com 01/05/2009 Since I mvoed this blog to Wordpress, I have used the Redirection plugin by [...]</description>
		<content:encoded><![CDATA[<p>[...] , and sometimes do not seem to justify the hassle involved in doing the upgraded. But version 2.7   Wordpress 2.7 breaks the Redirection plug-in? &#8211; tdaxp.com 01/05/2009 Since I mvoed this blog to Wordpress, I have used the Redirection plugin by [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->