<?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: Use WordPress 2.1.1?  Please Upgrade to WP 2.1.2!</title>
	<atom:link href="http://www.blogherald.com/2007/03/03/use-wordpress-211-please-upgrade-to-wp-212/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blogherald.com/2007/03/03/use-wordpress-211-please-upgrade-to-wp-212/</link>
	<description>The leading source of news covering social media and the blogosphere.</description>
	<lastBuildDate>Mon, 13 Feb 2012 06:52:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Should You Consider Human Translation For Your Blog? at The Blog Herald</title>
		<link>http://www.blogherald.com/2007/03/03/use-wordpress-211-please-upgrade-to-wp-212/comment-page-1/#comment-174396</link>
		<dc:creator>Should You Consider Human Translation For Your Blog? at The Blog Herald</dc:creator>
		<pubDate>Wed, 14 Mar 2007 11:27:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/03/03/use-wordpress-211-please-upgrade-to-wp-212/#comment-174396</guid>
		<description>[...] And so we have decided to remove the plugin altogether. For a while, after we first installed it, it worked great and brought in some decent traffic, especially on some of the international news stories. But after the recent WP upgrade, we&#8217;ve met with some technical difficulties, and there seems no light at the end of that tunnel, even with several consultations with the plugin author (we can&#8217;t seem to figure out what exactly is wrong with our installation/server). At any rate, most foreign language speakers observe machine translated articles as crude and barely readable as genuine translation anyway. They are too literal, and devoid of usable context. [...]</description>
		<content:encoded><![CDATA[<p>[...] And so we have decided to remove the plugin altogether. For a while, after we first installed it, it worked great and brought in some decent traffic, especially on some of the international news stories. But after the recent WP upgrade, we&#8217;ve met with some technical difficulties, and there seems no light at the end of that tunnel, even with several consultations with the plugin author (we can&#8217;t seem to figure out what exactly is wrong with our installation/server). At any rate, most foreign language speakers observe machine translated articles as crude and barely readable as genuine translation anyway. They are too literal, and devoid of usable context. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress Wednesday: Mandatory WordPress Update, WordPress Attack, WordPress.com New Features at The Blog Herald</title>
		<link>http://www.blogherald.com/2007/03/03/use-wordpress-211-please-upgrade-to-wp-212/comment-page-1/#comment-173016</link>
		<dc:creator>WordPress Wednesday: Mandatory WordPress Update, WordPress Attack, WordPress.com New Features at The Blog Herald</dc:creator>
		<pubDate>Wed, 07 Mar 2007 16:26:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/03/03/use-wordpress-211-please-upgrade-to-wp-212/#comment-173016</guid>
		<description>[...] WordPress 2.1.2 Mandatory Upgrade: As was reported last week, the latest upgrade of WordPress was attacked from a server breach and everyone was incredibly helpful in spreading the world that a new replacement and updated (and better protected) version is now available. This is a mandatory full upgrade. Due to the nature of the new version, there are no upgrade only files available. Don&#8217;t wait. Do this now. [...]</description>
		<content:encoded><![CDATA[<p>[...] WordPress 2.1.2 Mandatory Upgrade: As was reported last week, the latest upgrade of WordPress was attacked from a server breach and everyone was incredibly helpful in spreading the world that a new replacement and updated (and better protected) version is now available. This is a mandatory full upgrade. Due to the nature of the new version, there are no upgrade only files available. Don&#8217;t wait. Do this now. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle</title>
		<link>http://www.blogherald.com/2007/03/03/use-wordpress-211-please-upgrade-to-wp-212/comment-page-1/#comment-172468</link>
		<dc:creator>Lorelle</dc:creator>
		<pubDate>Tue, 06 Mar 2007 08:01:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/03/03/use-wordpress-211-please-upgrade-to-wp-212/#comment-172468</guid>
		<description>Always glad to help. ;-)</description>
		<content:encoded><![CDATA[<p>Always glad to help. ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brVincce</title>
		<link>http://www.blogherald.com/2007/03/03/use-wordpress-211-please-upgrade-to-wp-212/comment-page-1/#comment-172322</link>
		<dc:creator>brVincce</dc:creator>
		<pubDate>Mon, 05 Mar 2007 23:58:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/03/03/use-wordpress-211-please-upgrade-to-wp-212/#comment-172322</guid>
		<description>tnx for this! I visited the WP site linked here and upgrading now...</description>
		<content:encoded><![CDATA[<p>tnx for this! I visited the WP site linked here and upgrading now&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

