Ok, found the issue: apparently 776 is not working, but 775 is.

You can close this topic :-)

What is 776 ? And 775 ?

Permission settings.

I believe even those permissions are wrong.

These are PHP pages, like HTML pages that are interpreted by Apacge not run as shell scripts. That would be a security vulnerability.

Files should be 644 if Apache is being suexeced to run as the user, 664 if Apache enters the docroot with group access to 666 if Apache comes in as other (very dangerious).

Just like the directors should be set to 755, or 775, or God forbid 777.

Files should never have the execute bit set, unless they run as shell scripts.

For those who don't know how to derive these numbers:

4: Read / 2: Write / 1: Execute - Simply add up what you want.

Just my 2 cents!

If the fix of 775 over 776 fixed the loading of CSS files it would be because of the pemission on a directory, not on a file.

This would mean Apache is entering the directory with the security of "Other User" and switching 6 to 5 turns off write ability to Other and adds the execute ability on that directory. Which is what is needed to look into a directory for a file.

For limesurvey :

• ./tmp/ must be rwx for the web_user
• ./upload/ must be rwx by the web_user

Files and directory created in this dir :
. Files in this dir must be rw by the web_user
, directory created in this dir must be rwx by the web_user

For all other file (excepet when installing for config.php) must be readable (r) by web_user, directory mustr be readable and executabe (rx)

ADter : in tmp : we don't put php file if i don't make error. ANd we don't choose if it's executable : the web server do it, not LimeSUrvey.

Version 2.60 Build 150307 released