Tickets :: Comment on [#9140] backends.php.dist does not load configuration stanzas in .d directory

* Your Email Address
* Spam protection	Enter the letters below: . ..__..__.. . . \| \|\| \|\| \|\| \| \| \|__\|\|__\\|__\\|__\|\__\|
Comment	>> So, let's reboot the discussion: >> - First of all, these changes should go into the development aka git >> version of Horde and apps. > > Ok, it was just a proposal. > >> - It looks like we only support .d style loading for registry files >> from horde/config/registry.d/ >> - The rationale for loading registry stanzas from a directory makes >> sense, but what's the exact reason why you need this for backend >> configuration files in Turba/Ingo? > > Seemed like the straight forward thing to do to apply the same > strategy that is used for all other configuration files (at least in > Kolab) also to this one, given also that Kolab ships its own > 10-kolab_backends_base.php to override the dist backends.php: > http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolab-webclient/ingo/configuration/ingo-1.2.3/ > We applied the patch to be able to layer configurations (Horde, > Kolab, UCS) and ship 20-backends_ucs.php to have a standard clean > path to override (Horde, Kolab) settings if requirements change at > some point. > >> - If this going to be done correctly, it should be done in >> Horde::loadConfiguration(). > > Ok.
Attachment
Watch this ticket