General
Tweets on 2008-11-27
0- ok I can’t think of anything else. server is still slow, no conn problem, more than enough ram on server. i’m just gonna disable all plugins #
- now my server has crashed. great! #
- a geeks christmas wish list http://tinyurl.com/56xx2e (that would be me!) via @timoreilly #
- @hummingbird604 if you’re looking for housing in London…good luck
in reply to hummingbird604 # - couldn’t figure out what’s wrong with the server so I decided to reformat the hard disk. trying to reconfigure it now #
- reconfigured the server and it’s still fucking slow! #
Tweets on 2008-11-26
0- my server is very slow today for some reason. can’t even open a page! #
- dying to try out buddypress #
- @apeatling didn’t know you had test site up. I’ll give it a go right away. thx for the heads-up in reply to apeatling #
- @apeatling aren’t gravatars built into buddypress? in reply to apeatling #
- looks like my db server is the one with the problem. and since i’ve only got 1 db server the prob (whatever it is) slows down all my sites! #
- tried to change my flight home for christmas so I can attend the cambridge interview. just got the confirmation email frm malaysia airlines #
- no connection problems between db server and file servers…so where’s the problem??? #
- could someone pls visit my blog (joejacobs.org) and tell me whether it takes a while to load so I will know if it’s just an issue with my pc #
WordPress spell check fix
0Barry 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
Tweets on 2008-11-14
0- yay got an interview with Imperial College on 3 Dec. Hope it goes better than Bristol! #
WordPress spell check error
8I’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?