Summary | The Kolab share driver handling of share ids breaks creating shares in current Turba |
Queue | Turba |
Queue Version | HEAD |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | wrobel (at) horde (dot) org |
Requester | wrobel (at) horde (dot) org |
Created | 10/02/2007 (6485 days ago) |
Due | |
Updated | 05/09/2008 (6265 days ago) |
Assigned | 05/08/2008 (6266 days ago) |
Resolved | 05/09/2008 (6265 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Resolved
obsolete. I aparently overlooked this for a while. So this is resolved.
Assigned to Gunnar Wrobel
State ⇒ Assigned
solve for the 3.2 final release.
State ⇒ Not A Bug
to fix this before Horde 4. Closing as not a bug.
different Kolab apps and instead uses the name provided in the
set('name') call.
This breaks the way Turba currently creates shares and the attached
patch provides a workaround. I believe this can only be fixed in a
correct way once the Share interface can be changed again.
issue but this patch would likely break lots of stuff for other share
enabled backends, your patch would replace the share_name
(datatree_name) with the share_id (datatree_id) when creating the
user's default share, but we use the datatree_name everywhere else in
the code.
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ The Kolab share driver handling of share ids breaks creating shares in current Turba
Queue ⇒ Turba
New Attachment: HK-GW-Fix_share_id_change.patch
State ⇒ Unconfirmed
different Kolab apps and instead uses the name provided in the
set('name') call.
This breaks the way Turba currently creates shares and the attached
patch provides a workaround. I believe this can only be fixed in a
correct way once the Share interface can be changed again.