Details
-
Type: Improvement
-
Status: Done/Fixed
-
Priority: Minor
-
Resolution: Won't Fix
-
Affects Version/s: 3.1
-
Fix Version/s: 4.3.0
-
Component/s: Core CiviCRM
-
Labels:None
Description
updateConfigBackend shouldn't be needed most of the time (with drupal at least)
"CiviCRM will attempt to detect the new values that should be used.", but hasn't really worked for me after migrating a site elsewhere.
Proposed steps:
1. Let updateConfigBackend detect that its settings are wrong.
2. Fill in the proper settings (code might already be there, as it's saying).
3. Errors that are caused by wrong settings (elsewhere in the code base) should be fed into 1., manually.
4. Automate 3.