Yesterday, I installed MODx (1.0.2) on my remote server for a new project and when I got the the file/directory permissions check, everything passed - which never happens. I thought it was odd and went to check the actual permissions on the directories and files and the installer read them incorrectly and I did have to set them (as usual). Also, once installed and logged into the Manager, I did not get the usual notification of incorrect permission on /manager/includes/config.inc.php.
Has anyone ever had this happen before or have any idea why it might have misread all of the permissions? I’ve done dozens of MODx installations on the same server (Rackspace - Cloud Sites) and never had this happen. I also did a local install at the same time without any problems, so I don’t think it’s the install package.
-
MODX Staff
- 10,725 Posts
Is it possible they switched to running PHP as the user account, i.e. (suExec)? This would then not require you to change any permissions.
I would have thought it would be something like that except the actual permissions on the folders and files were not correct and needed to be set manually anyway. It seemed that MODx just read them incorrectly.
-
☆ A M B ☆
- 24,524 Posts
The permissions will not appear to be set "correctly"; the point of phpsuexec and friends is that you don’t have to have any world-writable permissions. The user is switched to the owner of the script when it is run, (which is what suexec means; switch user execute) so the php scripts you uploaded can write to any of the folders and files, since they are also owned by you. The correct permissions should be 755 for directories and 644 for files.
Thanks, Susan. That explains the folder permissions, which were in fact set to 755 and 644. But it doesn’t explain that it also checked "OK" for the existence and writability of /manager/includes/config.inc.php when the file actually did not exist on the server - unless the installer knew it had permission to create that file?
LOL! See how I learn things on here? Thanks!
