Author Topic: File Ownership - Best Practices for Code Updates (Read 977 times)

gbear · May 06, 2008, 09:16:28 pm

Hi -

I'm updating just a few things in our CiviCRM install - for instance changing the event dashboard.tpl, and Event.php code. I'm running in a Drupal environment, and when I installed CiviCRM it made the file ownership user and group "33"

Is there any issue with using chown on that to make it the user:group the same as my FTP - really just for ease of FTPing code updates.

Thanks
-Greg

Donald Lobo · May 08, 2008, 03:03:23 am

we do not change the file ownership / mode knowingly of any CiviCRM files. There are parts of the 'files' directory (templates_c) that is managed by Smarty. I think it creates files/directories as the http user. the 'files' directory needs to be readable/writable by the web

in 2.0 and prior, you should create and use a custom template directory for all your modifications.

in 2.1 we've also introduced a custom code directory where you can store modified copies of the code files

lobo

CiviCRM Community Forums (archive)

News:

Author Topic: File Ownership - Best Practices for Code Updates (Read 977 times)

gbear

File Ownership - Best Practices for Code Updates

Donald Lobo

Re: File Ownership - Best Practices for Code Updates