On Wed, Jul 17, 2013 at 11:27 PM, Michael Heydekamp listuser@freexp.de wrote:
Anyway, a general question with regards to the new config:
As I understand it, if a new additionl key is being invented, upon git-pull it will automatically go to defaults.inc.php, right? As long as it's not manually being included in the local config.inc.php as well, the default of this key in defaults.inc.php will apply, right?
Exactly.
But what if a key is being renamed/replaced by a different one... (we recently had this case, IIRC)? How does this work then, and how can we make sure that outdated config keys in the local config.inc.php will be replaced by the current ones (if the outdated key does exist there at all)?
The rcube_installer class (which is used by update.sh) has a mapping of renamed config options and alters the local config file accordingly. If the installer/update script doesn't have the permission to write new configs directly, a list of renamed properties is displayed which you then need to update manually.
~Thomas