Details
-
Type: Improvement
-
Status: Done/Fixed
-
Priority: Trivial
-
Resolution: Fixed/Completed
-
Affects Version/s: 2.2.8, 3.0
-
Fix Version/s: 3.0
-
Component/s: None
-
Labels:None
Description
The following code is executed when the civicrm db is moved (there may be other reasons, too?):
echo "Error: Could not create directory: $path.<p>If you have moved your database from a development install to a production install and the directory paths are different, please set the column config_backend in the civicrm_domain table to NULL. You will need to reinitialize your settings in the production install.<p>";
Is the following more helpful to users (and will it maybe keep the development team from having to answer newbie questions)?
echo "Error: Could not create directory: $path.<p>If you have moved your civicrm database, there are several steps you will need to follow. They are detailed in the CiviCRM wiki document Moving an Existing Installation to a New Server or Location. The fix for the specific problem that caused this error msg to be displayed is to set the column config_backend in the civicrm_domain table to NULL, followed by running updateConfigBackend. <p>";
[I'm a CiviCRM newbie, so perhaps my improvement could be improved?]
I did check the 3.0 beta – the error msg is the same.