1
JamesN
Struggling with Protector 3.1 install
  • 2008/8/29 19:07

  • JamesN

  • Just popping in

  • Posts: 16

  • Since: 2008/8/28


xoops - 2.0.18.1
Protector - 3.1

I'm simply trying to install it.

My hosting is with godaddy, so I have no folder called htdocs unless the root of my web folder is htdocs.

Here is the general setup....

www.MYSITE.com <-- think of as root. Nothing here.
www.MYSITE.com/x <--- where XOOPS was installed. url to get to main XOOPS site.

In the www.MYSITE.com area I created a /trust folder. Here is where I copied the contents of Xoops_Trust_Path from the protector zip.

I've edited my www.MYSITE.com/x/mainfile.php and added the location of the /trust folder.

I uploaded the module to the /../x/module folder and installed successfully.

I'm now to the point of doing this (from the beginners sticky)

Quote:
Once you've installed the module, go back and open mainfile.php again. There are some more changes you will need to make to activate Protector on your site. You can read the complete instructions in /xoops_trust_path/modules/protector/docs/readme, but here is the excerpt

define('XOOPS_GROUP_ADMIN', '1');
define('XOOPS_GROUP_USERS', '2');
define('XOOPS_GROUP_ANONYMOUS', '3');

<span style="color: #ff0000;">include( XOOPS_TRUST_PATH . '/modules/protector/include/precheck.inc.php' ) ;</span>
if (!isset($xoopsOption['nocommon']) <span style="color: #0000ff;">&& XOOPS_ROOT_PATH != ''</span> ) {
include XOOPS_ROOT_PATH."/include/common.php";
}
<span style="color: #ff0000;">include( XOOPS_TRUST_PATH . '/modules/protector/include/postcheck.inc.php' ) ;</span>




My mainfile.php does not have alot of that. Here is what mine looks like from that section of it...

Quote:
define('XOOPS_GROUP_ADMIN', '1');
define('XOOPS_GROUP_USERS', '2');
define('XOOPS_GROUP_ANONYMOUS', '3');

foreach ( array('GLOBALS', '_SESSION', 'HTTP_SESSION_VARS', '_GET', 'HTTP_GET_VARS', '_POST', 'HTTP_POST_VARS', '_COOKIE', 'HTTP_COOKIE_VARS', '_REQUEST', '_SERVER', 'HTTP_SERVER_VARS', '_ENV', 'HTTP_ENV_VARS', '_FILES', 'HTTP_POST_FILES', 'xoopsDB', 'xoopsUser', 'xoopsUserId', 'xoopsUserGroups', 'xoopsUserIsAdmin', 'xoopsConfig', 'xoopsOption', 'xoopsModule', 'xoopsModuleConfig', 'xoopsRequestUri') as $bad_global ) {
if ( isset( $_REQUEST[$bad_global] ) ) {
header( 'Location: '.XOOPS_URL.'/' );
exit();
}
}

if (!isset($xoopsOption['nocommon']) && XOOPS_ROOT_PATH != '') {
include XOOPS_ROOT_PATH."/include/common.php";
}
}
?>



Do I just need to add the above from the example? Is this a version conflict? Is there documentation not in french? Is my folder structure ok? Lastly, ever since I uploaded a new mainfile.php to the /../x/ I get this at the top of the admin portion

Quote:
WARNING: File /home/content/j/p/n/jpnorberg/html/x/mainfile.php is writeable by the server.
Please change the permission of this file for security reasons.
in Unix (444), in Win32 (read-only)

2
stefan88
Re: Struggling with Protector 3.1 install
  • 2008/8/29 19:32

  • stefan88

  • Community Support Member

  • Posts: 1086

  • Since: 2004/9/20


Hi,


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


before

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


and after that add

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



so final result will be:

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' ) ;


you may also look for a better place for your trust path - if you have protected folder outside your site
..

3
JamesN
Re: Struggling with Protector 3.1 install
  • 2008/8/29 19:47

  • JamesN

  • Just popping in

  • Posts: 16

  • Since: 2008/8/28


thankyou! I'll give all that a try.

Quote:
you may also look for a better place for your trust path - if you have protected folder outside your site


as for this... your saying I need a folder that isn't even part of my www.MYSITE.com? Maybe somewhere protected on the same server? I am very confused with this part of the install.

Anyone else using godaddy hosting and protector?

4
Anonymous
Re: Struggling with Protector 3.1 install
  • 2008/8/29 19:59

  • Anonymous

  • Posts: 0

  • Since:


Hi,

I've seen this a few times - not your fault as its easy to do.

Quote:
JamesN wrote:

<span style="color: #ff0000;">include( XOOPS_TRUST_PATH . '/modules/protector/include/precheck.inc.php' ) ;</span>
if (!isset($xoopsOption['nocommon']) <span style="color: #0000ff;">&& XOOPS_ROOT_PATH != ''</span> ) {
include XOOPS_ROOT_PATH."/include/common.php";
}
<span style="color: #ff0000;">include( XOOPS_TRUST_PATH . '/modules/protector/include/postcheck.inc.php' ) ;</span>



Try removing the code that I've highlighted in red the above quote.

HTH

5
JamesN
Re: Struggling with Protector 3.1 install
  • 2008/8/29 21:12

  • JamesN

  • Just popping in

  • Posts: 16

  • Since: 2008/8/28


that got it. thanks!


Another question... what is a quick and easy way to test to see if it is working?

6
stefan88
Re: Struggling with Protector 3.1 install
  • 2008/8/30 5:15

  • stefan88

  • Community Support Member

  • Posts: 1086

  • Since: 2004/9/20


Hi,

Quote:
your saying I need a folder that isn't even part of my www.MYSITE.com?


Yes. That is the idea, but the web server still needs access to that folder and in some setups that will not be posible. In that case it will be in your site. I do not use godaddy, so can't help on that.

Quote:
Another question... what is a quick and easy way to test to see if it is working?


Go to protector admin and check "Security Advisory" ...

..

7
konadu
Re: Struggling with Protector 3.1 install
  • 2008/8/31 13:57

  • konadu

  • Not too shy to talk

  • Posts: 116

  • Since: 2005/11/27


need some quick protector 3.1 help.

my website has been hack 10 times in 2 weeks.

I installed AntiDos and the hacking stopped for about a month and today it is back.

I am trying to install protector 3.1 but the install instructions are very confusing.

I have 2 questions concerning installing protector 3.1
1 - when i unzip the file protector-3.1.zip i get and "html" folder and "xoops_trust_path" folder. I have copied the protector folder in the "html" folder into my XOOPS modules on my website.

The question is where do i copy the content of xoops_trust_path" to.

Do i copy it to my website root folder? and do i copy on the "protector" folder in the "xoops_trust_path" or i should copy the whole "xoops_trust_path" to my root of the website.

This is pretty confusing for me and i need help in solving this before my website become entirely hacked...

Thanks.

Will be standing by for a quick response

SOS!

Login

Who's Online

165 user(s) are online (108 user(s) are browsing Support Forums)


Members: 0


Guests: 165


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