Fri, 10 Apr 2026 17:02:34 +0000 https://bugs.horde.org/ticket/7034 use user's id of a user's default share Contrary to most other Horde applications (imp, kronolith, ingo), turba chooses a random identifier when creating a missing user's default share. The other mentioned applications choose the user authentication id as it is reasonably unique for that purpose. I propose to adapt turba to that practice if no arguments exist against it. Sun, 06 Jul 2008 19:46:37 +0000 https://bugs.horde.org/ticket/7034#t47307 Unlike the other apps that you mentioned, Turba allows the configuration of any number of both shared and unshared sources, so just using the user name to create a new 'default' share would not work since it's possible to have more than one shared source. Sun, 06 Jul 2008 19:59:27 +0000 https://bugs.horde.org/ticket/7034#t47308 > Unlike the other apps that you mentioned, Turba allows the > configuration of any number of both shared and unshared sources, so > just using the user name to create a new 'default' share would not > work since it's possible to have more than one shared source. Horde 3.1 worked with datatree_name=uid. We have some scripts writing in the Horde database when ldap server is modified (name of the adressbook, ldap entry deleted, ...). Those scripts are based on the uid. I tried the patch and it works fine. The first adressbook created has datatree_name=uid and the others have a number. What kind of problem do you think about ? Wed, 30 Jul 2008 11:21:09 +0000 https://bugs.horde.org/ticket/7034#t47909