XOOPS Version: 2.0.13.2
Module Name/Version:
PHP Version: PHP 4.3.4
MySQL Version: MySQL 4.0.26
Web Server Software (Apache/IIS/Other): Apache
Operating System:
Theme you are using: Default
Custom template: (Yes/No) No
PHP Debug Messages:
MySQL Debug Messages:
Smarty Debug Messages:
A full description of the issue:XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run

http://www.beforeyouown.com is the website, although it's obviously down.

I have read several threads with solutions to this issue, but I still cannot figure out the problem with mine. I had XOOPS up and running for a couple of months with no problems. Nothing had changed, I did not install any new modules, etc and I all the sudden get this message.

I've read through the documentation also but that hasn't helped.

I have re-uploaded the mainfile.php and other ones also but it did not fix it. All the settings in mainfile should be correct since it was working perfectly before.

Any help or suggestions would be appreciated.

Thanks,
Joy

something is wrong with your virtual path or physical path in your mainfile. how are these setup?

Thanks for responding and trying to help.

I have XOOPS installed in my root folder. The exact virtual path I'm not sure of. It's shared hosting and it WAS working just fine.

Here is what is in the mainfile.php:
/hsphere/local/home/frogdesi/beforeyouown.com

frogdesi is my user name and then all the domains are listed under it. The other part before that, I'm not sure if it's set up right according to the server.

I did read in previous threads about this that there was a problem with the "hsphere" part of this path.?

Can you help me resolve it? I just don't understand why it was working before and now it's not.

Thanks in advance,
Joy

Also this issue is well documented here

THANK YOU THANK YOU THANK YOU.

I did the same as you.. changed the value to 0 and it's working now.

I can't thank you enough. I read through a lot of threads about this, but never came across yours.

Thanks,
Joy

Glad to be of assistance

I'd chase up your web host though regarding the physical path values of their server though so that you're not forced to disable the check.