Running a freshly installed XOOPS 2.5.0 , and have installed Protector from the system / modules part of XOOPS.

Continuing to get these error messages ..

404 - /public_html/modules/protector/css
referer: http://example.com/modules/protector/admin/index.php?page=advisory

404 - /public_html/XOOPS_TRUST_PATH
referer: http://example.com/modules/protector/admin/index.php?page=advisory

As Protector comes "with" XOOPS 2.5.0 , I am reporting this as an XOOPS core bug. Some info ..

I have this structure ..

/home/username/
/home/username/public_html
/home/username/secretpathname/
/home/username/secretpathname/renamed_xoops_data
/home/username/secretpathname/renamed_xoops_lib

Here is the mainfile.php ...



When I look at admin | protector , it seems the paths are looking okay. For example, where you define IP's to ban, it has the full pathname correctly.

The 'security advisor' TAB in protector has a link up the top which says "Check php files inside TRUST_PATH are private (it must be 404,403 or 500 error" , and that link is resolved incorrectly. It has resolved to http://example.com/secretpathname/renamed_xoops_lib/modules/protector/public_check.php , which is wrong, it should be /home/username/secretpathname/renamed_xoops_lib/modules/protector/public_check.php

Thanks,

Peter

Peter, make a simple test:

1) move renamed_xoops_lib and renamed_xoops_data to:
/home/username/public_html

2) update mainfile.php with the new paths

3) clear cache

4) Try to run XOOPS again.

If it works OK, it means that you don't have a proper access to the /home/username/secretpathname/ directory, and you should talk to your host provider.

Hi Mamba,

I'd be hesitant to do those 4 steps, as XOOPS is running just fine. I only have the core XOOPS installed, plus installed Protector from the core. Have added/installed xreaggregator which is running okay (except a 404 there, minor).

I can actually 'do' everything okay in XOOPS, no problems, just that the server logs are filling up with 404's from Protector. :)

I did the install as XOOPS wanted it, that is, when any path had the wrong perms, I corrected it until it was okay, then proceeded.

I just logged in via SFTP and the permissions on /home/username/secretpathname/ directory are 755 , so that is okay.

I'm thinking that either ..

(i) Protector is doing this in other sites, and people don't take any notice of 404's

OR

(ii) Protector can handle ..

/home/username/public_html
/home/username/renamed_xoops_data
/home/username/renamed_xoops_lib

BUT (maybe) not ..

/home/username/public_html
/home/username/secretpathname/
/home/username/secretpathname/renamed_xoops_data
/home/username/secretpathname/renamed_xoops_lib

Although the path names are resolved just fine in mainfile.php

Thanks,

Peter

Quote:
There is no risk involved. Instead of moving, just copy the renamed_xoops_lib and renamed_xoops_data to:
/home/username/public_html.

By changing the paths in mainfile.php you're controlling which directories are being accessed by XOOPS, and you can see if the Protector works correctly in /home/username/public_html.

After that, you can change the paths back to /home/username/secretpathname/ in mainfile.php and you're done.

Just make sure that you clear cache each time after the path changes in mainfile.php