| Summary | Turba: Adding a new addressbook | 
| Queue | Kolab | 
| Type | Bug | 
| State | Resolved | 
| Priority | 1. Low | 
| Owners | jan (at) horde (dot) org | 
| Requester | thomas.jarosch (at) intra2net (dot) com | 
| Created | 05/30/2008 (6367 days ago) | 
| Due | |
| Updated | 06/13/2008 (6353 days ago) | 
| Assigned | 05/31/2008 (6366 days ago) | 
| Resolved | 06/13/2008 (6353 days ago) | 
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No | 
Taken from Chuck Hagenbuch
State ⇒ Resolved
http://cvs.horde.org/diff.php/turba/lib/Turba.php?r1=1.163&r2=1.164&ty=u
submits the id?
submits the id?
creating a share, no?
Isn't it a bit odd that the client code requesting a new share also
submits the id?
creating a share, no?
Taken from Gunnar Wrobel
Assigned to Jan Schneider
Taken from Thomas Jarosch
New Attachment: turba-fix-add-Share.patch
with "md5(mt_rand())" 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.
State ⇒ Assigned
Assigned to Thomas Jarosch
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Turba: Adding a new addressbook
Queue ⇒ Kolab
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
after upgrading to Turba HEAD, newly added addressbooks using the
Kolab backend don'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