Fri, 10 Apr 2026 05:21:35 +0000 https://bugs.horde.org/ticket/3701 custom hook support for backend selection The attached file contains two patches against ingo-h3-1.1 conf.xml.patch for config/conf.xml Ingo.php.patch for lib/Ingo.php They add suport for one custom hook for backend Selection (_ingo_hook_selectBackend) Tue, 28 Mar 2006 12:16:39 +0000 https://bugs.horde.org/ticket/3701#t18185 Looks good. Tue, 28 Mar 2006 12:47:37 +0000 https://bugs.horde.org/ticket/3701#t18192 Can you update your patch to use Horde::callHook() instead, use a different hook name (_ingo_hook_backend_select), and provide an example for horde/config/hooks.php.dist? Mon, 24 Apr 2006 13:14:03 +0000 https://bugs.horde.org/ticket/3701#t19394 Sure. Here you have an example of the custom hook. I need a little more time to address the rest of the issues. I'll upload it tomorrow. Mon, 24 Apr 2006 16:42:42 +0000 https://bugs.horde.org/ticket/3701#t19402 Here's the updated version of the patch with the requested changes. I've opened an enhancement ticket for the passwd module to implement a similar functionality (see ticket #3821) I'll update it accordingly when we close all the pending issues with this ticket Tue, 25 Apr 2006 10:54:55 +0000 https://bugs.horde.org/ticket/3701#t19452 The patch to Ingo.php does not apply for me. Also, is this really something that can't be done inside the backends.php config file? Wed, 24 May 2006 05:56:14 +0000 https://bugs.horde.org/ticket/3701#t20578 > The patch to Ingo.php does not apply for me. I've just downloaded back the patch and a fresh copy of Ingo-h3-1.1.1 from ftp.horde.org and it applies without errors to both files. Wed, 24 May 2006 12:51:45 +0000 https://bugs.horde.org/ticket/3701#t20601 Sorry if I was unclear - new features should always be against HEAD, not a release version (see http://horde.org/source/contribute.php), so that's what I was applying it against. What about my question on why this is necessary? Wed, 24 May 2006 13:57:22 +0000 https://bugs.horde.org/ticket/3701#t20602 > Sorry if I was unclear - new features should always be against HEAD, > not a release version (see http://horde.org/source/contribute.php), > so that's what I was applying it against. Ok. Sorry for that. I use to work on stable releases to get the patches working on our production system as fast as possible. I'll modify it using a CVS checkout if you finally find this patch useful. > What about my question on why this is necessary? Well, getBackend() in lib/Ingo.php selects the backend wich its 'preferred' field equals $_SERVER['SERVER_NAME'] or $_SERVER['HTTP_HOST'] In our University we have only one URL to access the webmail system but three different IMAPservers wich need different backends (procmail and sieve, the 3rd server is Exchange), so the unpatched system always uses the same backend. Currently, I have no idea on how to achieve this using backends.php Wed, 24 May 2006 19:46:02 +0000 https://bugs.horde.org/ticket/3701#t20638 Instead of using hooks, or the preferred method, and instead of defining all 3 backends in backends.php, use your hooks code right in backends.php to figure out which backend the user belongs to, then define only that one. Wed, 24 May 2006 20:38:35 +0000 https://bugs.horde.org/ticket/3701#t20639 Thanks for the tip. I will try it. I forget that the config files are php files too, so they allow this degree of flexibility. Thu, 25 May 2006 20:35:22 +0000 https://bugs.horde.org/ticket/3701#t20680 I think that sometimes we forget it, too. :) Fri, 26 May 2006 03:43:14 +0000 https://bugs.horde.org/ticket/3701#t20689 Just for the record, our solution, based on Chuck's suggestions, is discussed here: http://lists.horde.org/archives/ingo/Week-of-Mon-20070528/001345.html Se also: http://wiki.horde.org/IngoMulti Thu, 30 Dec 2010 08:38:14 +0000 https://bugs.horde.org/ticket/3701#t61267