Anything's Possible
WordPress spell check error
I’ve been having this problem for the past couple of months with the spell checking in WordPress. An error window with a whole lotta gibberish in it pops up every time I try to do a spell check. This is the recorded error message from my error logs:
Warning: fsockopen() [function.fsockopen]: unable to connect to ssl://www.google.com:443 (Unable to find the socket transport “ssl” – did you forget to enable it when you configured PHP?)
I’ve done some searches on Google and the only possible solution that I found was to recompile PHP with support for CURL and openSSL. So I tried that but I still get an error message. Anyone got any ideas what’s wrong?
| Print article | This entry was posted by Joe Jacobs on 5th November, 2008 at 4:48 pm, and is filed under General. Follow any responses to this post through RSS 2.0. You can leave a response or trackback from your own site. |
about 1 year ago
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’t make sense. Check your configuration or go line by line to see how or why that’s needed.
about 1 year ago
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!
about 1 year ago
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!
about 1 year ago
Yea that’s what I said!
about 11 months ago
anyone get an answer to this?
about 11 months ago
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/
about 11 months ago
Do you remember what exactly the issue was?
Thanks,
about 11 months ago
I think it was a TinyMCE issue