Barry of Clearskys.net has found a fix for the spellcheck error. It was a problem with the headers sent by the script. Commenting the encoding header did the trick

//header('Content-Encoding: UTF-8');

the header is in the file rpc.php which is in wp-includes/js/tinymce/plugins/spellcheck

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?

Got quite a bit done today. Most importantly, I’ve [finally] transferred all my sites over to my spankin’ new server! Brad has very kindly hosted ALL my sites on his server for the past year or so. I’m sure he’s glad I’ve finally buggered off!

I’ve also decided to install WordPress on the site. I’ve put it off for way too long. This design (Kubrick) will have to stay  though until I find the time to make my own.  Unfortunately, I still haven’t uploaded the scripts yet. I should have some time to do that tomorrow after college. In the meantime, if you need anything please email me at joe at hazardcell dot com.