<?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>Turba: Adding a new addressbook</title> 
  <pubDate>Fri, 10 Apr 2026 09:21:07 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/6797</link> 
  <atom:link rel="self" type="application/rss+xml" title="Turba: Adding a new addressbook" href="https://bugs.horde.org/ticket/6797/rss" /> 
  <description>Turba: Adding a new addressbook</description> 
 
   
   
  <item> 
   <title>Hello together,



after upgrading to Turba HEAD, newly adde</title> 
   <description>Hello together,



after upgrading to Turba HEAD, newly added addressbooks using the Kolab backend don&#039;t get automatically added to the addressbook list.

Does this work for you, Gunnar?



I took a quick look at the prefs saved on disc, the addressbook list array looks like it contains md5-hashes of the actual folder/share names???



Thomas

</description> 
   <pubDate>Fri, 30 May 2008 14:19:28 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6797#t45698</link> 
  </item> 
   
  <item> 
   <title>I&#039;ve found the source of the bug: $driver-&gt;createShare() get</title> 
   <description>I&#039;ve found the source of the bug: $driver-&gt;createShare() get called with &quot;md5(mt_rand())&quot; for $share_id. The Kolab driver later updates the share id with the encoded folder name. Attached patch updates the share_id with the real id.



Please see the attached patch.

</description> 
   <pubDate>Tue, 03 Jun 2008 09:02:55 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6797#t45867</link> 
  </item> 
   
  <item> 
   <title>There are probably many places where we use the share id aft</title> 
   <description>There are probably many places where we use the share id after creating a share, no?</description> 
   <pubDate>Tue, 03 Jun 2008 10:14:19 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6797#t45871</link> 
  </item> 
   
  <item> 
   <title>&gt; There are probably many places where we use the share id a</title> 
   <description>&gt; There are probably many places where we use the share id after 

&gt; creating a share, no?



I took a quick look now at kronolith, nag and mnemo, they all do it right.



Isn&#039;t it a bit odd that the client code requesting a new share also submits the id?

</description> 
   <pubDate>Tue, 03 Jun 2008 12:34:52 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6797#t45872</link> 
  </item> 
   
  <item> 
   <title>&gt; Isn&#039;t it a bit odd that the client code requesting a new s</title> 
   <description>&gt; Isn&#039;t it a bit odd that the client code requesting a new share also 

&gt; submits the id?



No, because we want the default shares to have the user name as the id.</description> 
   <pubDate>Tue, 03 Jun 2008 13:04:51 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6797#t45873</link> 
  </item> 
   
  <item> 
   <title>&gt;&gt; Isn&#039;t it a bit odd that the client code requesting a new </title> 
   <description>&gt;&gt; Isn&#039;t it a bit odd that the client code requesting a new share also

&gt;&gt; submits the id?

&gt;

&gt; No, because we want the default shares to have the user name as the id.



Ok. lease apply the patch anyway, it&#039;s broken using Kolab.

</description> 
   <pubDate>Fri, 06 Jun 2008 09:29:59 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6797#t46045</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in CVS for this ticket:

http://cvs.h</title> 
   <description>Changes have been made in CVS for this ticket:

http://cvs.horde.org/diff.php/turba/lib/Turba.php?r1=1.163&amp;r2=1.164&amp;ty=u</description> 
   <pubDate>Fri, 13 Jun 2008 08:46:07 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6797#t46387</link> 
  </item> 
   
  <item> 
   <title>Committed.</title> 
   <description>Committed.</description> 
   <pubDate>Fri, 13 Jun 2008 08:46:15 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6797#t46388</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
