File Permissions Updated with Upgrades & Installs

[gregmarsh]

I was wondering if there are any plans to create a utility that would scan a sugar directory structure and set all the file defaults (Sugar only I guess). Every time I install an update I have to fix a sea of directories and files and to be honest I am wondering why this very boring activity is necessary.

With out the changes of course I do not have the correct msgs showing and in some cases the pages don't display but on the other hand it is very frustrating and I have had to expose sites temporarily to hacking when they had to be immediately available and I did not have the time to tweak the individual files or directories.

This should not be a major task for the attribute definition for each file can be set up on mass by file type on mass and then tweaked from there. This would also force the development team to think about permissions which is always a good thing since permissions probably cause the most bugs for "Working Code" out there.

Any build software would easily be able to generate a fix file that could adapt to each OS and if done with a simple structure anyone adding to sugar could simply #include (or similar) their own file definitions.

Gone would be the need to guess between a 664 and 665 etc. - why directories switch to 770 versus 775 and why there seems to be this random change of 0255 for some but not all the structures.

The other thing is if it could run from within the installation imagine the speed difference between this and running via FTP.

All the best.

[Ramblin]

I just wrote a little bash script that resets all the file permissions

#!/bin/bash

cd /var/www/html

chown -R asterisk:asterisk crm

chmod -R 755 crm

cd crm

chmod -R 775 cache
chmod -R 775 custom
chmod -R 775 data
chmod -R 775 modules
if [ -s upload ]
     then
	chmod -R 775 upload
fi
chmod 644 .htaccess
chmod 664 config.php
chmod 664 config_override.php
chmod 664 sugarcrm.log

Put the above in a file at the same level as (ie not in <sugar_root>, but in /var/www/html/
make it executable

Before AND After each update (or after each Repair & Rebuild) run the script

Your permissions are set according to SugarCRM Guidelines