Well if your scripts name is "logout.php" and the error says the scripts name is "logout.wgs" then you have a more serious problem than the simple session handler... thou I'm betting this was just a typo on your part <Grinz>
Anyways lots of people have been having problems with the session_destroy function, I for one havn't, probably because I use a custom session handler with MySQL instead of files (see "session_set_save_handler()" for more info), I believe most of the trouble they have is due to the file system and php not having been granted deletion privliges. So my suggestion is to check the access priv's for the php executable/module and maybe even for the webserver itself. And failing that try playing with the custom session handlers a bit, personaly I find them much faster and more reliable when coupled with MySQL or some other database.
