<?xml version="1.0" encoding="iso-8859-1"?><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: WordPress: Server Error 500 beim Veröffentlichen</title>
	<atom:link href="http://www.finanzberater-aktuell.de/wordpress/wordpress-server-error-500-beim-veroffentlichen.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.finanzberater-aktuell.de/wordpress/wordpress-server-error-500-beim-veroffentlichen.html</link>
	<description>Interessante Artikel zu den Themen Geld - Aktien - Vorsorge - Rente - Versicherungen</description>
	<lastBuildDate>Sat, 13 Feb 2010 15:29:30 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Von: hr-</title>
		<link>http://www.finanzberater-aktuell.de/wordpress/wordpress-server-error-500-beim-veroffentlichen.html/comment-page-1#comment-57</link>
		<dc:creator>hr-</dc:creator>
		<pubDate>Thu, 25 Jan 2007 10:17:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.finanzberater-aktuell.de/wordpress/wordpress-server-error-500-beim-veroffentlichen.html#comment-57</guid>
		<description>So sieht z.B. ein Logeintrag vom Smart Update Pinger aus:

01/25/07 11:14:33 Pinging services (new post: “WordPress: Server Error 500 beim Veröffentlichen”) ...
01/25/07 11:14:33 - http://ping.wordblog.de/ was successfully pinged (extended format)
01/25/07 11:14:33 - http://bblog.com/ping.php was successfully pinged (extended format)
01/25/07 11:14:34 - http://blogsearch.google.com/ping/RPC2 was successfully pinged (extended format)
01/25/07 11:14:35 - http://rpc.pingomatic.com/ was successfully pinged (extended format)
01/25/07 11:14:35 - http://www.bloglines.com/ping was successfully pinged (extended format



Ein Beispiel für fehlerhafte Pings:

01/24/07 06:24:23 - http://weblogs.com/ could not be pinged. Error message: “parse error. not well formed”
01/24/07 07:52:02 - http://ping.blogg.de/ could not be pinged. Error message: “transport error - could not open socket: 110 Connection timed out”</description>
		<content:encoded><![CDATA[<p>So sieht z.B. ein Logeintrag vom Smart Update Pinger aus:</p>
<p>01/25/07 11:14:33 Pinging services (new post: “WordPress: Server Error 500 beim Veröffentlichen”) &#8230;<br />
01/25/07 11:14:33 &#8211; <a href="http://ping.wordblog.de/" rel="nofollow"></a><a href='http://ping.wordblog.de/'>http://ping.wordblog.de/</a> was successfully pinged (extended format)<br />
01/25/07 11:14:33 &#8211; <a href="http://bblog.com/ping.php" rel="nofollow"></a><a href='http://bblog.com/ping.php'>http://bblog.com/ping.php</a> was successfully pinged (extended format)<br />
01/25/07 11:14:34 &#8211; <a href="http://blogsearch.google.com/ping/RPC2" rel="nofollow"></a><a href='http://blogsearch.google.com/ping/RPC2'>http://blogsearch.google.com/ping/RPC2</a> was successfully pinged (extended format)<br />
01/25/07 11:14:35 &#8211; <a href="http://rpc.pingomatic.com/" rel="nofollow"></a><a href='http://rpc.pingomatic.com/'>http://rpc.pingomatic.com/</a> was successfully pinged (extended format)<br />
01/25/07 11:14:35 &#8211; <a href="http://www.bloglines.com/ping" rel="nofollow"></a><a href='http://www.bloglines.com/ping'>http://www.bloglines.com/ping</a> was successfully pinged (extended format</p>
<p>Ein Beispiel für fehlerhafte Pings:</p>
<p>01/24/07 06:24:23 &#8211; <a href="http://weblogs.com/" rel="nofollow"></a><a href='http://weblogs.com/'>http://weblogs.com/</a> could not be pinged. Error message: “parse error. not well formed”<br />
01/24/07 07:52:02 &#8211; <a href="http://ping.blogg.de/" rel="nofollow"></a><a href='http://ping.blogg.de/'>http://ping.blogg.de/</a> could not be pinged. Error message: “transport error &#8211; could not open socket: 110 Connection timed out”</p>
]]></content:encoded>
	</item>
</channel>
</rss>
