Posted on: 2014/6/20 7:57
Re: XOOPS 2.5.7 Final Release Issues
I have a small problem with the following link in protector (tab 'security advisory')That check PHP files inside TRUST_PATH are set to read-only (it must be 404.403 or 500 error)
The link points to:http://myserver/www
/xoops_lib/modules/protector/public_check.php for local installation)
but have to point to:http://myserveur/xoops_lib/modules/protector/public_check.php
There are additionnal www.
My analysis after several tests and fresh install:
This occurs only if 2.5.7 is installed (not tested with 2.5.6) on a debian based server
(I do not have any other Linux distributions to test) in local or intranet
In my case, tested on two different machines:
- Ubuntu 12.04 LTS server with PHP 5.3.10 and Apache 2.2.22.
- Debian 7 with PHP 5.4.4 and Apache 2.2.22.
- Default LAMP installation under / var / www
(Hey, it looks like the three additionnal w)
So far nothing special and a website works perfectly here.
If I install a 2.5.7 at this point, I have the problem of protector link which does not work with the additionnal www.
But if I create a subdirectory (with the well alias) eg / var/www/site1 and I install 2.5.7 here the protector link is good.
I'd like to know if anyone else has the same problem on a LAMP configuration or if someone could test to confirm whether or not the problem is in protector or the configuration of my machines?