<?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>Kommentare zu: Upgraded to WP 2.9 &#8211; and ended up with an HTTP error 500</title>
	<atom:link href="http://www.justria.com/2009/12/21/upgraded-to-wp-2-9-and-ended-up-with-an-http-error-500/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.justria.com/2009/12/21/upgraded-to-wp-2-9-and-ended-up-with-an-http-error-500/</link>
	<description>software, internet, etc.</description>
	<lastBuildDate>Wed, 01 Sep 2010 22:40:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Von: Peter P.</title>
		<link>http://www.justria.com/2009/12/21/upgraded-to-wp-2-9-and-ended-up-with-an-http-error-500/comment-page-1/#comment-89</link>
		<dc:creator>Peter P.</dc:creator>
		<pubDate>Thu, 31 Dec 2009 17:48:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.justria.com/?p=164#comment-89</guid>
		<description>Hi! 
Thanks for these tips! 
Now everything is up and running again fine.

BTW: Happy new year to everybody! ;-)</description>
		<content:encoded><![CDATA[<p>Hi!<br />
Thanks for these tips!<br />
Now everything is up and running again fine.</p>
<p>BTW: Happy new year to everybody! ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: upgrade to WP 2.9 &#8211; if auto-upgrade doesn&#8217;t go auto at justRIA</title>
		<link>http://www.justria.com/2009/12/21/upgraded-to-wp-2-9-and-ended-up-with-an-http-error-500/comment-page-1/#comment-84</link>
		<dc:creator>upgrade to WP 2.9 &#8211; if auto-upgrade doesn&#8217;t go auto at justRIA</dc:creator>
		<pubDate>Tue, 22 Dec 2009 00:00:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.justria.com/?p=164#comment-84</guid>
		<description>[...] you might end up with a blank page or one, which indicates a HTTP error 500. In this have a look at my previous post, which solves a problem with changed PHP setting of certain providers (namely [...]</description>
		<content:encoded><![CDATA[<p>[...] you might end up with a blank page or one, which indicates a HTTP error 500. In this have a look at my previous post, which solves a problem with changed PHP setting of certain providers (namely [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Alex Otero</title>
		<link>http://www.justria.com/2009/12/21/upgraded-to-wp-2-9-and-ended-up-with-an-http-error-500/comment-page-1/#comment-83</link>
		<dc:creator>Alex Otero</dc:creator>
		<pubDate>Mon, 21 Dec 2009 09:14:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.justria.com/?p=164#comment-83</guid>
		<description>Thanks for the tips! I&#039;ve upgraded yesterday I got exactly that, an error 500 couldn’t get to the back end. Luckily I had made a backup of all the files and just put them back on.. Gonna try yours later today! Thanks again!</description>
		<content:encoded><![CDATA[<p>Thanks for the tips! I&#8217;ve upgraded yesterday I got exactly that, an error 500 couldn’t get to the back end. Luckily I had made a backup of all the files and just put them back on.. Gonna try yours later today! Thanks again!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
