XOOPS Physical Path

I am trying to install to remote web server. Everything goes fine until I get the following message. "XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run." I am letting my newbie side show but I have tried every everything I can think of to set the root path. I have the server root path but I cannot get it to work. I have prefaced it with // the ip address the web address, etc. but to no avail. If anyone can help the newbie discover the obvious I appreciate it. I could not find the answer in the install documentation.

Thanks

Sorry, no answer, I have the SAME problem. Anyone have a clue?

Here are my rootpath.php results, so Im pretty sure that is correct.

Your root path is/usr/local/etc/httpd/htdocs-test
without string replace:/usr/local/etc/httpd/htdocs-test

Help!

Thanks

You can bypass that check by editing mainfile.php and making the following change:

define('XOOPS_CHECK_PATH', 0);

Thanks for the reply. That doesnt seemed to have helped however. I also can sometimes get

Warning: offset not contained in string in /usr/local/etc/httpd/htdocs-test/install/index.php on line 256

or

Warning: offset not contained in string in ../mainfile.php on line 53
XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run.

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.