[dev] [commits] Horde branch master updated. a0c1ee118b71c24b4ecb12da20606822490992ec

[Jan Schneider]

Zitat von Michael M Slusarz <slusarz at horde.org>:

> Quoting Jan Schneider <jan at horde.org>:
>
>> commit a0c1ee118b71c24b4ecb12da20606822490992ec
>> Author: Jan Schneider <jan at horde.org>
>> Date:   Sat Feb 12 18:43:18 2011 +0100
>>
>>    Provide default backends.php where it makes sense. Add configuration
>>    options to allow administrators to pick the backends to use.
>
> I really don't like this change, at least with respect to IMP.  If  
> we are going to store backend configuration in a separate file, that  
> config needs to be exclusive to that file.  The "available" config  
> option in conf.php is overkill and confusing.
>
> I would rather see backends.php shipped with a 'disabled' option set  
> to true for each example.  Then an admin simply needs to remove the  
> 'disabled' option to activate a given config example.  Better yet,  
> when an admin manually adds an entry to backends.php, it will just  
> work as expected - no need to change anything in conf.php.

That won't work, because the idea is that admins don't touch  
backends.php (or any .php configuration file for that matter) at all.  
Those are like any other .php file shipped by Horde, i.e. they will be  
overwritten with the next update.

If admins want to customize an existing backend, or add a new one,  
they need to do that in a *.local.php file. This is a bit more  
complicated than editing an example in-place though, thus we need a  
way for a less exeperienced admin to easily pick the backend to use.  
For more experience admins it's a snap to update the configuration  
after adding new backends.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/