PEAK XOOPS - XOOPS 2.0.14 and Protextor 2.56 in englishin japanese

XOOPS 2.0.14 and Protextor 2.56

  • You cannot open a new topic into this forum
  • Guests cannot post into this forum
Previous post - Next post | Parent - Children.1 | Posted on 2006/7/1 9:02
jenz  企霹始   Posts: 1
Hello. I just upgraded from XOOPS 2.0.13 to XOOPS 2.0.14 and after completing the upgrade, when I have:

include( XOOPS_ROOT_PATH . '/modules/protector/include/precheck.inc.php' ) ;
if (!isset($xoopsOption['nocommon']) && XOOPS_ROOT_PATH != '' ) {
include XOOPS_ROOT_PATH."/include/common.php";
}
include( XOOPS_ROOT_PATH . '/modules/protector/include/postcheck.inc.php' ) ;

in mainfile.php, I cannot load any of my web site from any computer. I tried to temporary disable Protector, but I still get blank pages. The only thing that allows people to view my site is when the above text is taken out of mainfile.php. Any help would be greatly appreciated as I love this module!

Thanks.
Votes:8 Average:10.00
Previous post - Next post | Parent - Children.1 .2 | Posted on 2006/7/5 20:56
SquALED  企霹始   Posts: 5
Im getting the exact same prob - worked fine in 2.0.12a but now ive upgraded to 2.0.14 (after the site was hacked by the way) im getting blank pages aand the rescue .php is no help.

Im getting this error:

Fatal error: Cannot redeclare class xos_kernel_xoops2 in /home/www/**mysite**/include/common.php on line 40
All errors (0) queries (7) blocks (0) extra (0) timers (3)

Any ideas Joe?

Thanks

Sq
Votes:8 Average:10.00
Previous post - Next post | Parent - Children.1 | Posted on 2006/7/6 9:16
skalpa  企霹始   Posts: 4
include/common.php is included several times....

Now there's a test in mainfile.php to prevent this, and it actually doesn't happen in normal cases (I normally test protector compatibility before doing releases).

I could have made a mistake, but here I think more that the cause is coming from a badly edited mainfile.php (the include lines for protector and common.php may have been moved out of the if ( !defined("XOOPS_MAINFILE_INCLUDED") ) { clause).

You may want to change the include line like this, it should fix the problem:
In mainfile.php, replace this line
		include XOOPS_ROOT_PATH."/include/common.php";
with this
		include_once XOOPS_ROOT_PATH."/include/common.php";
Votes:8 Average:10.00
Previous post - Next post | Parent - Children.1 | Posted on 2006/7/6 18:35
SquALED  企霹始   Posts: 5
Thanks for the reply but no change - still getting the error mentioned in the previous post

Sq
Votes:8 Average:10.00
Previous post - Next post | Parent - No child | Posted on 2006/7/8 3:30
Dave_L  惧霹始 From: Virginia, USA  Posts: 35
Could you post your mainfile.php? Use the [ code ] tag and replace private info (actual path, password, etc.) with "xxxxxx".
Votes:6 Average:10.00
Previous post - Next post | Parent - No child | Posted on 2006/7/8 6:26
GIJOE  黎扦烦菱   Posts: 4110
I'm sorry my too late answer.

xos_kernel_xoops2 ...?

2.0.14 looks far different from 2.0.13.x

Though I know I have to make independent environment for 2.0.14, I'm very busy in Juny because of my work and watching Tour de France.

BTW, I guess there is no problem in mainfile.php

I know some modules include common.php after including mainfile.php with 'nocommon'.

List the modules you've installed.
Votes:9 Average:10.00

  Advanced search


Login
Username or e-mail:

Password:

Remember Me

Lost Password?

Register now!