<?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"
	>
<channel>
	<title>Comments on: Some things you can&#8217;t say in WordPress</title>
	<atom:link href="http://philcrissman.com/2005/11/29/some-things-you-cant-say-in-wordpress/feed" rel="self" type="application/rss+xml" />
	<link>http://philcrissman.com/2005/11/29/some-things-you-cant-say-in-wordpress</link>
	<description>Web Development, startups, entrepreneurship, books, art, and other stuff</description>
	<pubDate>Fri, 21 Nov 2008 16:41:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: philcrissman</title>
		<link>http://philcrissman.com/2005/11/29/some-things-you-cant-say-in-wordpress#comment-280</link>
		<dc:creator>philcrissman</dc:creator>
		<pubDate>Tue, 29 Nov 2005 19:39:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.philcrissman.com/2005/11/29/some-things-you-cant-say-in-wordpress/#comment-280</guid>
		<description>Thanks for the reply, Jim. Yeah, apparently it is a wider problem with WordPress... I posted it mostly to add to the few other posts I found about it. If it's a bug, it should be fixed; if it's by design (blocking executable commands for security purposes) then there should be a list of words so that it isn't just a shock when you're told you have an error... ;-)</description>
		<content:encoded><![CDATA[<p>Thanks for the reply, Jim. Yeah, apparently it is a wider problem with WordPress&#8230; I posted it mostly to add to the few other posts I found about it. If it&#8217;s a bug, it should be fixed; if it&#8217;s by design (blocking executable commands for security purposes) then there should be a list of words so that it isn&#8217;t just a shock when you&#8217;re told you have an error&#8230; ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Walton</title>
		<link>http://philcrissman.com/2005/11/29/some-things-you-cant-say-in-wordpress#comment-279</link>
		<dc:creator>Jim Walton</dc:creator>
		<pubDate>Tue, 29 Nov 2005 15:19:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.philcrissman.com/2005/11/29/some-things-you-cant-say-in-wordpress/#comment-279</guid>
		<description>I had something similar happen, where I couldn't post like that.  It's been awhile and I removed parts of my post until I narrowed it down to a specific word or phrase.  I copied the original post back in, changed the offending culprit and it was fine.  I didn't google the issue at all, I just assumed it was isolated to me and didn't concern myself with the source, although I should have.  I was probably just busy and ready to move on.  I don't recall at all what the word or phrase was, but it was identical to what you describe.  Sorry I can't offer any insight other than I feel your pain.</description>
		<content:encoded><![CDATA[<p>I had something similar happen, where I couldn&#8217;t post like that.  It&#8217;s been awhile and I removed parts of my post until I narrowed it down to a specific word or phrase.  I copied the original post back in, changed the offending culprit and it was fine.  I didn&#8217;t google the issue at all, I just assumed it was isolated to me and didn&#8217;t concern myself with the source, although I should have.  I was probably just busy and ready to move on.  I don&#8217;t recall at all what the word or phrase was, but it was identical to what you describe.  Sorry I can&#8217;t offer any insight other than I feel your pain.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.389 seconds -->
