<?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: Error 404 When Publishing or Saving Post</title>
	<atom:link href="http://abing.gotdns.com/posts/2006/wordpress-error-404-when-publishing-or-saving-post/feed/" rel="self" type="application/rss+xml" />
	<link>http://abing.gotdns.com/posts/2006/wordpress-error-404-when-publishing-or-saving-post/</link>
	<description>Because you can never have too many blogs on the Internet...</description>
	<lastBuildDate>Thu, 05 Nov 2009 19:27:52 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Crazy &#8216;404 Not Found&#8217; WordPress Publishing Error &#8212; Don&#8217;t Let This Bite You Like It Bit Me &#124; Mastering New Media :: Jason Van Orden</title>
		<link>http://abing.gotdns.com/posts/2006/wordpress-error-404-when-publishing-or-saving-post/comment-page-1/#comment-12309</link>
		<dc:creator>Crazy &#8216;404 Not Found&#8217; WordPress Publishing Error &#8212; Don&#8217;t Let This Bite You Like It Bit Me &#124; Mastering New Media :: Jason Van Orden</dc:creator>
		<pubDate>Thu, 05 Nov 2009 19:27:52 +0000</pubDate>
		<guid isPermaLink="false">http://abing.gotdns.com/2006/07/06/40/#comment-12309</guid>
		<description>&lt;p&gt;[...] I finally turned to Google. A simple search for 404 error WordPress publish immediately revealed the answer. To sum up the rather geeky explanation, a security setting on the server was causing my post to be [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] I finally turned to Google. A simple search for 404 error WordPress publish immediately revealed the answer. To sum up the rather geeky explanation, a security setting on the server was causing my post to be [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Erro 404 ao salvar ou publicar posts no WordPress</title>
		<link>http://abing.gotdns.com/posts/2006/wordpress-error-404-when-publishing-or-saving-post/comment-page-1/#comment-10723</link>
		<dc:creator>Erro 404 ao salvar ou publicar posts no WordPress</dc:creator>
		<pubDate>Sun, 05 Jul 2009 22:40:08 +0000</pubDate>
		<guid isPermaLink="false">http://abing.gotdns.com/2006/07/06/40/#comment-10723</guid>
		<description>&lt;p&gt;[...] o Terminus A Quo e o Software Engeneering in the Loose, de onde retirei a solução o problema é relativo a alguma [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] o Terminus A Quo e o Software Engeneering in the Loose, de onde retirei a solução o problema é relativo a alguma [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: laneolson.ca &#124; Page Not Found When Posting or Editing WordPress Posts</title>
		<link>http://abing.gotdns.com/posts/2006/wordpress-error-404-when-publishing-or-saving-post/comment-page-1/#comment-10080</link>
		<dc:creator>laneolson.ca &#124; Page Not Found When Posting or Editing WordPress Posts</dc:creator>
		<pubDate>Fri, 22 May 2009 19:16:29 +0000</pubDate>
		<guid isPermaLink="false">http://abing.gotdns.com/2006/07/06/40/#comment-10080</guid>
		<description>&lt;p&gt;[...] tried to repost the item as a new post. I still received the 404 error! After some Googling I found this blog post which outlined some solutions to this problem. It appears that some people have had some luck using [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] tried to repost the item as a new post. I still received the 404 error! After some Googling I found this blog post which outlined some solutions to this problem. It appears that some people have had some luck using [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: jim</title>
		<link>http://abing.gotdns.com/posts/2006/wordpress-error-404-when-publishing-or-saving-post/comment-page-1/#comment-8881</link>
		<dc:creator>jim</dc:creator>
		<pubDate>Tue, 17 Mar 2009 13:14:37 +0000</pubDate>
		<guid isPermaLink="false">http://abing.gotdns.com/2006/07/06/40/#comment-8881</guid>
		<description>&lt;p&gt;I&#039;ve found that this error is set off by encoding as well.&lt;/p&gt;

&lt;p&gt;Usually when you try to copy/paste from Word. Workaround for that is to copy from Word, paste into Notepad and then copy again and paste into wordpress.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve found that this error is set off by encoding as well.</p>

<p>Usually when you try to copy/paste from Word. Workaround for that is to copy from Word, paste into Notepad and then copy again and paste into wordpress.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Wordpress 404 after editing post &#124; Jo0Lz.nl ♥ Home of the Evil Genius!</title>
		<link>http://abing.gotdns.com/posts/2006/wordpress-error-404-when-publishing-or-saving-post/comment-page-1/#comment-7958</link>
		<dc:creator>Wordpress 404 after editing post &#124; Jo0Lz.nl ♥ Home of the Evil Genius!</dc:creator>
		<pubDate>Thu, 15 Jan 2009 10:58:32 +0000</pubDate>
		<guid isPermaLink="false">http://abing.gotdns.com/2006/07/06/40/#comment-7958</guid>
		<description>&lt;p&gt;[...] installations I maintain, didn&#8217;t have this problem. After a while, someone pointed me to this [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] installations I maintain, didn&#8217;t have this problem. After a while, someone pointed me to this [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Web  Design  Romania</title>
		<link>http://abing.gotdns.com/posts/2006/wordpress-error-404-when-publishing-or-saving-post/comment-page-1/#comment-7898</link>
		<dc:creator>Web  Design  Romania</dc:creator>
		<pubDate>Tue, 06 Jan 2009 02:35:18 +0000</pubDate>
		<guid isPermaLink="false">http://abing.gotdns.com/2006/07/06/40/#comment-7898</guid>
		<description>&lt;p&gt;Thank you for writing this. I tried the htaccess soultions before finding your article and was hoping there still is a chance to do this another way. But since you said I have to manually find the bad word if the htaccess doesn&#039;t work you spared me of searches .. phew.&lt;/p&gt;

&lt;p&gt;One thing I recommend: instead of rewriting a word with the table you gave, replace the bad word with a good one. That&#039;s how i did and this pared me of meticulos thing to do with the table.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thank you for writing this. I tried the htaccess soultions before finding your article and was hoping there still is a chance to do this another way. But since you said I have to manually find the bad word if the htaccess doesn&#8217;t work you spared me of searches .. phew.</p>

<p>One thing I recommend: instead of rewriting a word with the table you gave, replace the bad word with a good one. That&#8217;s how i did and this pared me of meticulos thing to do with the table.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Micah Tapman</title>
		<link>http://abing.gotdns.com/posts/2006/wordpress-error-404-when-publishing-or-saving-post/comment-page-1/#comment-5200</link>
		<dc:creator>Micah Tapman</dc:creator>
		<pubDate>Sat, 29 Mar 2008 17:12:41 +0000</pubDate>
		<guid isPermaLink="false">http://abing.gotdns.com/2006/07/06/40/#comment-5200</guid>
		<description>&lt;p&gt;Nice description of the posting problem. For troubleshooting, it may be faster to use the 50% rule. Try posting the first half of your post, see if you get the error. If you do, cut that 50% in half (now it&#039;s 25% of your total post) and post it again. Rinse and repeat. This should cut the time it takes to find the code that&#039;s causing the problems.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Nice description of the posting problem. For troubleshooting, it may be faster to use the 50% rule. Try posting the first half of your post, see if you get the error. If you do, cut that 50% in half (now it&#8217;s 25% of your total post) and post it again. Rinse and repeat. This should cut the time it takes to find the code that&#8217;s causing the problems.</p>]]></content:encoded>
	</item>
</channel>
</rss>
