<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Enhance vinfo hook</title> 
  <pubDate>Fri, 10 Apr 2026 04:38:52 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/7889</link> 
  <atom:link rel="self" type="application/rss+xml" title="Enhance vinfo hook" href="https://bugs.horde.org/ticket/7889/rss" /> 
  <description>Enhance vinfo hook</description> 
 
   
   
  <item> 
   <title>The attached patch (against FRAMEWORK_3 tag) adds two (hopef</title> 
   <description>The attached patch (against FRAMEWORK_3 tag) adds two (hopefully) useful changes to the vinfo hook:

#1 adds the possibility to modify the selected mailserver during login. This allows us to select the correct mailserver by parsing the login username. I have also created a simple example in hooks.php.dist.

#2 passes the value of $_SESSION[&#039;imp&#039;][&#039;user&#039;] as an array item. So you don&#039;t have to get the value from the session. This is just a api correction for the $value-param needed for #1.



If necessary I can create a patch for HEAD aswell.</description> 
   <pubDate>Sun, 25 Jan 2009 18:48:01 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7889#t51955</link> 
  </item> 
   
  <item> 
   <title>Why not use a pre- or post-authenticate hook for this? If th</title> 
   <description>Why not use a pre- or post-authenticate hook for this? If that&#039;s not currently possible - it might not be, though it might just require mucking with $_SESSION data directly - then let&#039;s work towards making it possible. I think the pre/post authenticate hooks are a much cleaner way to do this sort of thing than the vinfo hook, which I&#039;d like to phase out.</description> 
   <pubDate>Wed, 28 Jan 2009 02:59:37 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7889#t52037</link> 
  </item> 
   
  <item> 
   <title>As far as I remember I tried to use pre/post_auth in the fir</title> 
   <description>As far as I remember I tried to use pre/post_auth in the first place but it would&#039;ve required more work (e.g. a lot of session variables will be set before authenticate()-call). Also there&#039;s currently no way to get the value of the selected server in any session variable before login.</description> 
   <pubDate>Wed, 28 Jan 2009 09:52:19 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7889#t52042</link> 
  </item> 
   
  <item> 
   <title>If you&#039;re parsing the server from the username anyway, why d</title> 
   <description>If you&#039;re parsing the server from the username anyway, why do you need the selected server? And, like I said, I&#039;d really prefer to make it easier to do things with the pre- and post-auth hooks instead of extending the vinfo hook, even if it would be harder *now*.</description> 
   <pubDate>Wed, 28 Jan 2009 15:02:53 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7889#t52046</link> 
  </item> 
   
  <item> 
   <title>We&#039;ve one installation for our webspace- and our dedicated c</title> 
   <description>We&#039;ve one installation for our webspace- and our dedicated customers. Webspace customers are uniquely identifiable while dedicated customers are not. Thus they have to select their own server in the server list. Webspace customers just use a dummy entry &quot;autodetection&quot; which triggers the hook.



I&#039;m fully with you in expanding the pre-/post-hooks. I just wanted to point out why I used the vhook for now.</description> 
   <pubDate>Thu, 29 Jan 2009 17:06:05 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7889#t52099</link> 
  </item> 
   
  <item> 
   <title>Please post this in the wiki if you want to share it; going </title> 
   <description>Please post this in the wiki if you want to share it; going forwards we&#039;ll enhance the pre/post hooks.</description> 
   <pubDate>Tue, 10 Feb 2009 16:54:39 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7889#t52455</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
