prevent conflicts on templates_c CRM-16604

[tttp]

http://civicrm.stackexchange.com/questions/2923/civicrm-does-not-have-permission-to-write-temp-files/2937#2937

Prevent "CiviCRM does not have permission to write temp files in ... templates_c/..." error messages.
"Drush command terminated abnormally due to an unrecoverable error"

Two users are trying to access the temp files (where, for instance, the compiled templates are stored): www-data (when it's accessed from the website) and the sysadmin that run drush commands

By default, all these temporary files can only modified by the user that created it, so sometimes it's the sysadmin, sometimes it's the webserver user

---

• CRM-16604: drush and www-data conficts on templates_c permission

[mlutfy]

Shouldn't it be defined before including the civicrmSettingsFile? (otherwise, the civicrm.settings.php defines the constant, so the condition will never be true?)
Coding style: the comment should be on a separate line, above the line concerned.

[totten]

When doing drush cvapi system.flush or drush cvupdb, won't this prevent us from flushing the actual templates_c cache?

[tttp]

@totten indeed, having separate caches is making the clear cache from command line pointless ;(

PR isn't usable as it is then. Plan B?

Can we test if it's a command that actually needs to access the main template_c cache (eg. system.flush or cc cvupdb)?