Hi More problems are coming to light caused by the disabling of fsockopen() just because of some few bad eggs misusing them. On top of several important functions not working in a web directory script using this function (see http://forums.x10hosting.com/free-hosting/28003-some-pages-not-fully-loading.html ) I discovered several functions in Drupal, including the inbuilt cron, that is crucial for a number things is not working. One cannot make some crucial system updates or changes and of course stuff depending on cron, like rss feeds update are now useless as the cron module uses it. I also see for "no apparent reason" when submitting content the categorization option, ie of the content, eg of a cake recipe to the Cakes section or a military joke to Military Jokes has vanished without anything done by me, meaning the taxonomy module responsible for this has been affected, etc etc. Meanwhile, at the above link, the script writer of the web directory script suggests the administrator could at least selectively enable fsockopen() for some users (who can be watched) & gives a link at php.net how that could be achieved. He acknowledges the potential misuse of fsockopen(), but believes there is a way around this. Please at least consider that. PS. Could it be the automerging of some posts can be misleading as one gets the impression it's the same post that eg. a moderator/administrator may assume has been read when it actually has some new information that may need to be acted upon? Some information for example in the above post, added hours later, was automerged & appears to be a mere small update of the original response to Coreys message - when I had added it as a new reply AFTER his to my original one.