42
Quote:
For example if the folder the file resides in is read write and execute enabled and the file is read only you are still able to delete and modify the file under the linux file system this is due to the fact that unix system is based on files and the files under a folder are considered to be the content of that particular folder, hence you can delete and modify the name of the files under the directory because you as owner have rights to modify the public directory (file's contents.)
Quote:
Again, I chmoded mainfile.php in 444, and got all the previous images for confirmation.
I launch the installation and, with no surprises what so ever, XOOPS successfully wrote the configuration informations in mainfile.php, while it should have been in Read Only.
Something's wrong here. YOU are the owner of public_html, not the server (usual usernames: www, wwwrun, apache, server,...), often apache isn't even part of the usergroup 'users'. If you visit the install trough the web, it is apache who writes in mainfile.php, not you. My conclusion here is that your public_html is chmodded (777) (or 77* if apache is part of 'users') if the first quote is true.
If your public_html is (777) either you chmodded it that way, or your host did something wrong, because public_html isn't supposed to be writable by anyone, not even ppl in the same usergroup.