<?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 spell check error</title>
	<atom:link href="http://joejacobs.org/2008/11/05/wordpress-spell-check-error/feed/" rel="self" type="application/rss+xml" />
	<link>http://joejacobs.org/2008/11/05/wordpress-spell-check-error/</link>
	<description>Anything&#039;s Possible</description>
	<lastBuildDate>Wed, 08 Feb 2012 00:35:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Joe Jacobs</title>
		<link>http://joejacobs.org/2008/11/05/wordpress-spell-check-error/comment-page-1/#comment-4709</link>
		<dc:creator>Joe Jacobs</dc:creator>
		<pubDate>Tue, 18 Aug 2009 05:43:19 +0000</pubDate>
		<guid isPermaLink="false">http://joejacobs.org/?p=169#comment-4709</guid>
		<description>I think it was a TinyMCE issue</description>
		<content:encoded><![CDATA[<p>I think it was a TinyMCE issue</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed</title>
		<link>http://joejacobs.org/2008/11/05/wordpress-spell-check-error/comment-page-1/#comment-4707</link>
		<dc:creator>Ed</dc:creator>
		<pubDate>Tue, 18 Aug 2009 04:57:32 +0000</pubDate>
		<guid isPermaLink="false">http://joejacobs.org/?p=169#comment-4707</guid>
		<description>Do you remember what exactly the issue was?
Thanks,</description>
		<content:encoded><![CDATA[<p>Do you remember what exactly the issue was?<br />
Thanks,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Jacobs</title>
		<link>http://joejacobs.org/2008/11/05/wordpress-spell-check-error/comment-page-1/#comment-4705</link>
		<dc:creator>Joe Jacobs</dc:creator>
		<pubDate>Tue, 18 Aug 2009 04:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://joejacobs.org/?p=169#comment-4705</guid>
		<description>For me the issue was with my web server. At that time, I was using Litespeed Web Server.

http://joejacobs.org/2008/11/21/wordpress-spell-check-fix/</description>
		<content:encoded><![CDATA[<p>For me the issue was with my web server. At that time, I was using Litespeed Web Server.</p>
<p><a href="http://joejacobs.org/2008/11/21/wordpress-spell-check-fix/" rel="nofollow">http://joejacobs.org/2008/11/21/wordpress-spell-check-fix/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed</title>
		<link>http://joejacobs.org/2008/11/05/wordpress-spell-check-error/comment-page-1/#comment-4704</link>
		<dc:creator>Ed</dc:creator>
		<pubDate>Tue, 18 Aug 2009 01:34:04 +0000</pubDate>
		<guid isPermaLink="false">http://joejacobs.org/?p=169#comment-4704</guid>
		<description>anyone get an answer to this?</description>
		<content:encoded><![CDATA[<p>anyone get an answer to this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Jacobs</title>
		<link>http://joejacobs.org/2008/11/05/wordpress-spell-check-error/comment-page-1/#comment-20</link>
		<dc:creator>Joe Jacobs</dc:creator>
		<pubDate>Sun, 16 Nov 2008 00:08:40 +0000</pubDate>
		<guid isPermaLink="false">http://joejacobs.org/?p=169#comment-20</guid>
		<description>Yea that&#039;s what I said!</description>
		<content:encoded><![CDATA[<p>Yea that&#8217;s what I said!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivan, Web-Impress.com</title>
		<link>http://joejacobs.org/2008/11/05/wordpress-spell-check-error/comment-page-1/#comment-19</link>
		<dc:creator>Ivan, Web-Impress.com</dc:creator>
		<pubDate>Fri, 14 Nov 2008 07:51:42 +0000</pubDate>
		<guid isPermaLink="false">http://joejacobs.org/?p=169#comment-19</guid>
		<description>I copied the function that was generating the previous error and ran it separately. It seemed to work fine. It tries to connect using 2 methods, first with CURL then with fsockopen. Both methods worked fine when I tested it but the spell check still isn’t workling!</description>
		<content:encoded><![CDATA[<p>I copied the function that was generating the previous error and ran it separately. It seemed to work fine. It tries to connect using 2 methods, first with CURL then with fsockopen. Both methods worked fine when I tested it but the spell check still isn’t workling!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Jacobs</title>
		<link>http://joejacobs.org/2008/11/05/wordpress-spell-check-error/comment-page-1/#comment-15</link>
		<dc:creator>Joe Jacobs</dc:creator>
		<pubDate>Mon, 10 Nov 2008 21:58:03 +0000</pubDate>
		<guid isPermaLink="false">http://joejacobs.org/?p=169#comment-15</guid>
		<description>I copied the function that was generating the previous error and ran it separately. It seemed to work fine. It tries to connect using 2 methods, first with CURL then with fsockopen. Both methods worked fine when I tested it but the spell check still isn&#039;t workling!</description>
		<content:encoded><![CDATA[<p>I copied the function that was generating the previous error and ran it separately. It seemed to work fine. It tries to connect using 2 methods, first with CURL then with fsockopen. Both methods worked fine when I tested it but the spell check still isn&#8217;t workling!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad</title>
		<link>http://joejacobs.org/2008/11/05/wordpress-spell-check-error/comment-page-1/#comment-14</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Mon, 10 Nov 2008 20:42:57 +0000</pubDate>
		<guid isPermaLink="false">http://joejacobs.org/?p=169#comment-14</guid>
		<description>It looks like a sample url.

ssl://www.google.com:443 to me would be the same as https://www.google.com. The ssl:// and use of port 443 is trying to open an ssl connection to google, but why your spell checker would do that doesn&#039;t make sense. Check your configuration or go line by line to see how or why that&#039;s needed.</description>
		<content:encoded><![CDATA[<p>It looks like a sample url.</p>
<p>ssl://www.google.com:443 to me would be the same as <a href="https://www.google.com" rel="nofollow">https://www.google.com</a>. The ssl:// and use of port 443 is trying to open an ssl connection to google, but why your spell checker would do that doesn&#8217;t make sense. Check your configuration or go line by line to see how or why that&#8217;s needed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

