Details
-
Type:
Improvement
-
Status: Done/Fixed
-
Priority:
Trivial
-
Resolution: Won't Fix
-
Affects Version/s: 3.4.5, 4.0.5
-
Fix Version/s: Unscheduled
-
Component/s: None
-
Labels:None
Description
Certain installations require the addition of settings_location.php for CiviCRM to locate the site configuration.
Typically this fixes issues with sites where the CiviCRM codebase is symlinked into place and it's not possible to discover the CiviCRM configuration by backing up a directory. However, it's also needed when calling civicrm/bin/*php scripts directly. In both cases, CiviCRM lacks the usual context to find the site configuration.
Issues with this approach are that -
1. It may require a site-specific "configuration" file inside the CiviCRM codebase. If the same CiviCRM code is deployed to dev / stage / live, then this location may be wrong. Configuration files should ideally live outside the module directory.
2. It does not play nicely with multisite installations on Drupal, because it ties the CiviCRM install directory to a specific site.
Drupal generally copes well without needing an equivalent to CIVICRM_CONFDIR, and I believe CiviCRM can do the same.