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=advisory404 - /public_html/XOOPS_TRUST_PATH
referer:
http://example.com/modules/protector/admin/index.php?page=advisoryAs 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 ...
le="color: #000000"><?php // XOOPS Physical Paths // Physical path to the XOOPS documents (served) directory WITHOUT trailing slash define('XOOPS_ROOT_PATH', '/home/username/public_html'); // For forward compatibility // Physical path to the XOOPS library directory WITHOUT trailing slash define('XOOPS_PATH', '/home/username/secretpathname/renamed_xoops_lib'); // Physical path to the XOOPS datafiles (writable) directory WITHOUT trailing slash define('XOOPS_VAR_PATH', '/home/username/secretpathname/renamed_xoops_data'); // Alias of XOOPS_PATH, for compatibility, temporary solution define("XOOPS_TRUST_PATH", XOOPS_PATH); // URL Association for SSL and Protocol Compatibility $http = 'http://'; if (!empty($_SERVER['HTTPS'])) { $http = ($_SERVER['HTTPS']=='on') ? 'https://' : 'http://'; } define('XOOPS_PROT', $http); // XOOPS Virtual Path (URL) // Virtual path to your main XOOPS directory WITHOUT trailing slash // Example: define('XOOPS_URL', 'http://example.com'); define('XOOPS_URL', 'http://example.com');
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
