skalpa, by the way, re the 2.0.6 to 2.0.7 update package and

"If this is the old release, get those files from one of the 2.0.6 to 2.0.7 packages: html/mainfile.dist.php html/install/index.php and html/include/common.php"

Why is the html/install/index.php file included? Should it be opened on the server after ftp'ing over all the newer html files and opening the upgrade/xoops_206_to_207.php file? There is no mention of how this file is used in the "!!EXTRA UPGRADE INSTRUCTIONS!! Please apply the patch as ususal, overwriting the original files with the ones from the patch. ..." instructions.

Dave_L, yes, that's what I wound up doing also; but I'm puzzled why that happened on that 2.0.6 to 2.0.7 update.

Unlike for the update on my LAN server, there was a glitch. Checking the site generated an error from the new "XOOPS_CHECK_PATH" code in the "mainfile.php" file: "XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run."

The define line used a parameter value of 1 rather than zero as in the "mainfile.dist.php" file [define('XOOPS_CHECK_PATH', 0);]. After changing the parameter value to 0, site access worked again.

Puzzling, since my XOOPS LAN server has a parameter value of 1 in the "mainfile.php" file, which works okay.

8-19-04 Update: There was an error in the XOOPS physical path, which probably was the issue. I discovered the discrepancy while doing another XOOPS installation which worked okay with "define('XOOPS_CHECK_PATH', 1);" on the same host.