XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Community Support forums / 
  3. Q and A 
  4.  / XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run.
Register
1
Clever
XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run.

  • 2006/5/26 13:30

  • Clever

  • Just popping in

  • Posts: 81

  • Since: 2004/4/24


I've been running a site smoothly for months - no changes have been made, etc. It's been wonderful...
Today I am getting this error:

XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run.

Is this the host screwing around, or something that I need to fix?
(btw - I applied the manual fix that skalpa posted for the mainfile.php file, no change)

Thanks for whatever insight you can provide.
The site is:

TASS Reunion Website


Thanks again!
2
phppp
Re: XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run.

  • 2006/5/26 13:53

  • phppp

  • XOOPS Contributor

  • Posts: 2857

  • Since: 2004/1/25


does it happen to specific modules or the whole site?
Your site is not accessible from my place

try to empty cache folder
3
Clever
Re: XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run.

  • 2006/5/26 13:59

  • Clever

  • Just popping in

  • Posts: 81

  • Since: 2004/4/24


It happens to the whole site...
I have tried to get in every which way.
I emptied the cache, but no change.

Thanks for the speedy reply!

Warmest regards,
Lisa
4
phppp
Re: XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run.

  • 2006/5/26 14:11

  • phppp

  • XOOPS Contributor

  • Posts: 2857

  • Since: 2004/1/25


if you site is not so sensitive to security, as a temporary workaround, change mainfile.php:
define('XOOPS_CHECK_PATH', 0);

Then try to find out what happens in
if ( XOOPS_CHECK_PATH && !@ini_get('safe_mode') ) {
...
}
5
Clever
Re: XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run.

  • 2006/5/26 14:22

  • Clever

  • Just popping in

  • Posts: 81

  • Since: 2004/4/24


OMG...
The mainfile.php is now 0 kb.
Empty.
Nothing in it.
What do I do?
6
Clever
Re: XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run.

  • 2006/5/26 15:35

  • Clever

  • Just popping in

  • Posts: 81

  • Since: 2004/4/24


The brilliant mind of my favourite French-Canadian (Marcan) is currently helping with this issue, but any suggestions are more than welcome!
I'm told PHP is working fine (says Marcan) and that this is an "interesting problem"...
7
Clever
Re: XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run.

  • 2006/5/26 20:59

  • Clever

  • Just popping in

  • Posts: 81

  • Since: 2004/4/24


THANKS, MARCAN!!!
I appreciate the help you gave me...
You were right - it was deeper than XOOPS - it WAS a new server configuration that altered something and the hosting company was able to track it down.
Your assistance in tracking down the problem and re-building mainfile.php was invaluable! I can't thank you enough!!!

Warmest regards,
Lisa
8
marcan
Re: XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run.

  • 2006/5/31 21:32

  • marcan

  • Just can't stay away

  • Posts: 824

  • Since: 2003/10/8


It was my pleasure Lisa

Cheers !
.:: marcan (aka mal aka Marc-André) ::.
.:: Open Source :: The SmartFactory ::.
.:: XOOPS Professional Services :: INBOX International ::.
9
tedsmith
Re: XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run.

  • 2006/7/28 18:55

  • tedsmith

  • Home away from home

  • Posts: 1151

  • Since: 2004/6/2 1


Also this issue is well documented here

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

366 user(s) are online (247 user(s) are browsing Support Forums)

Members: 0

Guests: 366

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits