Error response: <br /> <b>Warning</b>: fsockopen() [<a href='function.fsockopen'>function.fsockopen</a>]: unable to connect to ssl://www.google.com:443 (Unable to find the socket transport &quot;ssl&quot; - did you forget to enable it when you configured PHP?) in <b>D:\websites\*******\wp-includes\js\tinymce\plugins\spellchecker\classes\GoogleSpell.php</b> on line <b>86</b><br /> Could not open SSL connection to google.{"id":null,"result":[],"error":null?

There is a way hot to solve it: enable the php_curl extension in your php.ini. Just delete the “;” (semicolon) in front of this line: ;extension=php_curl.dll and you’re done. WordPress will now be able to check your spelling and suggest correct alternatives!

Any problems let me know.

BTW – it has nothing to do with any other library, simply just php_curl.dll library.

I’m super excited and would like to let you all know – especially the ones that have been stuck with a similar issue for some time: we have ThickBox working and running with DocuView and… DISPLAYING AUTOMATICALLY GENERATED PDFs (AS WELL AS NORMAL PDFs) IN MODAL WINDOW (and it works in FireFox 2+, IE6+, IE7, Opera 9.51, Safari Win… Mac testing follows successfully completed).

The link that helped me: http://codylindley.com/thickboxforum/comments.php?DiscussionID=303&page=1

I am still trying to get my head around the fact that the solution is as easy as adding all seven (7) characters: .show(). The forum member was solving displaying Flash, but it applies to PDF too.

*NEW UPDATE! I’m really really chuffed, pleased and ecstatic, hope it helps, by all means check the edited thickbox javascript file. The changes occur on lines #196 and #199, one is meant to append the aforementioned “.show()” at the end of each occurrence of “</iframe>” in the code.

Drop me a line should you struggle, drop me a line if it worked for you! Now we’re down to cracking generating PDF through COM (OpenOffice) via PHP.

Till then

Sometimes (and I don’t know why) the Skype installation enables as default the use of alternative ports – 80 and 443 to be precise. Now those ports are widely and commonly used by more than just Skype (take your localhost for instance, 443 is used for secure (https) connections). And we came across a scenario where Skype’s default settings wouldn’t enable stable connection to any remote machine runnig Windows.

The spoiler: to fix this go to: Tools > Options > Advanced > Connection > and uncheck “Use port 80 and 443 as alternatives for incoming connections” as of v3.6.0.248.

BTW – did you know Windows Skype doesn’t really work on Windows 2008 at all?

Update: Skype has released v3.8 several times now and even the Beta 4.0 seems to be working just fine on Windows 2008. Solved.