Author Topic: Make location of localised PHP and Templates more flexible (Read 1809 times)

ken · August 01, 2012, 07:25:08 pm

Hi,

It appears the location of the custom PHP and Template code needs to be situated under a directory derived from the CIVICRM_TEMPLATE_COMPILEDIR.

For me, that's currently under sites/default/files/civicrm in my Drupal install. As the PHP and templates are code, I'd prefer to store it under sites/all/modules as a module, to simplify configuration control.

When I try and set the custom PHP or templates directory outside the sites/default/files/civicrm tree I don't get an error, but the change doesn't stick. I assume this is because the directory stored is a path relative to the root (eg, sites/default/files/civicrm/local/php is stored as local/php in my case).

Ken

Erik Hommel · August 02, 2012, 12:41:23 am

Ken,
I do not have that problem in any of my installs? I usually keep my custom PHP and template dirs in /sites/all/modules, so outside of the civicrm tree. This makes upgrading a little easier...I have been in the situation where I have deleted my customizations during an upgrade :-)

ken · August 09, 2012, 01:51:39 am

It's a bug with multisite. I'll create a separate post with the details.

CiviCRM Community Forums (archive)

News:

Author Topic: Make location of localised PHP and Templates more flexible (Read 1809 times)

ken

Make location of localised PHP and Templates more flexible

Erik Hommel

Re: Make location of localised PHP and Templates more flexible

ken

Re: Make location of localised PHP and Templates more flexible