1
Burning
Protector & Xoops 2.4.0
  • 2009/10/26 21:44

  • Burning

  • Theme Designer

  • Posts: 1163

  • Since: 2006/8/22


hi'

I'm upgrading a XOOPS 2.3.3 site. Protector 3.40 is already installed.


• First question

Upgrade works fine, except those two error messages on all pages :
Quote:
Notice : Constant PROTECTOR_PRECHECK_INCLUDED already define in C:\wamp\www\xoops_lib\modules\protector\include\precheck.inc.php on line 10
Notice : Constant PROTECTOR_VERSION already define in C:\wamp\www\xoops_lib\modules\protector\include\precheck.inc.php on line 11


To hide those two messages, I have to modify mainfile.php and to comment two lines :
// include( XOOPS_TRUST_PATH . '/modules/protector/include/precheck.inc.php' ) ;
    
if (!isset($xoopsOption['nocommon']) && XOOPS_ROOT_PATH != '') {
        include 
XOOPS_ROOT_PATH."/include/common.php";
    
//include( XOOPS_TRUST_PATH . '/modules/protector/include/postcheck.inc.php' ) ;
    
}
}
?>


It is the right way to proceed ?


• Second question

I see there are some lines added in Protector available in XOOPS 2.4.0 package...

If I use original module available on GiJoe website, modules administration table does not display all items.

For next release of Protector module, it will be some change to do on original code ? Some explanations would be very useful about it (sorry if such explanations already exist, I haven't saw it )


Thanks

2
trabis
Re: Protector & Xoops 2.4.0
  • 2009/10/26 22:39

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


Hi Burning,
the version of protector 3.4 released with the 2.4 core has very small changes. This changes cover security breaks if module is on public folder and use of preloads to avoid hacking core. I don't see any relation between the "modules administration table does not display all items." and the changes made.

You should remove the lines

include( XOOPS_TRUST_PATH . '/modules/protector/include/precheck.inc.php' ) ;
include( XOOPS_TRUST_PATH . '/modules/protector/include/postcheck.inc.php' ) ;

from mainfile.php because they are not needed. Also, do not touch class/database/databasefactory.php. The hook is already present.

3
Burning
Re: Protector & Xoops 2.4.0
  • 2009/10/26 22:47

  • Burning

  • Theme Designer

  • Posts: 1163

  • Since: 2006/8/22


Thanks for your explanations
Upgrade process works fine !


Quote:
I don't see any relation between the "modules administration table does not display all items." and the changes made.

... I have made a lot of hacks on my XOOPS site, and as I'm not a developer, now all goes wrong ! Do you know I have manage to make my Debug mode disapear, also from database

Login

Who's Online

147 user(s) are online (100 user(s) are browsing Support Forums)


Members: 0


Guests: 147


more...

Donat-O-Meter

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

Latest GitHub Commits