Quote:

Sourceforge mirrors are taking some time to update their files and as the new release files are named as the 1st one it seems that some mirrors still give access to the 1st 2.0.7 release.

I've tried to download each package several times and it seems that only the full releases encounter the problem. So, if you want to get a full install but not to wait:
- Get a xoops-2.0.7.xxx from SF
- Check its content to know if you got the good one (the html/include/common.php file header should indicate 1.54)
- 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

skalpa.>

Any update on this issue? I installed the 2.0.7 release downloaded from the Aleron sourceforge mirror but the files in the ZIP are still outdated. This leads to the above problem under NT2000/IIS5 (but runs fine under Red Hat Fedora2 with Apache)
For the NT2K/IIS5 install, I tried to update the three files as suggested (from the 2.0.6 to 2.0.7 package, files are dated 6/15 and 6/17) but I then get a blank page instead of the "cannot run script" message.
Any help would be appreciated.

I was under the impression that if you set the XOOPS_CHECK_PATH
in the mainfile.php to 0 it bypassed the new security feature.
I personally set it to 1 but if I'm wrong could someone explain better.

In mainfile.php

define('XOOPS_CHECK_PATH', 0);

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.