| 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 | Gunnar Wrobel <p (at) rdus (dot) de> |
| Requester | Gunnar Wrobel <p (at) rdus (dot) de> |
| Created | 10/02/2007 (222 days ago) |
| Due | |
| Updated | 05/09/2008 (2 days ago) |
| Assigned | 05/08/2008 (3 days ago) |
| Resolved | 05/09/2008 (2 days ago) |
| Attachments | HK-GW-Fix_share_id_change.patch ![]() |
| Milestone | |
| Patch |
State ⇒ Resolved
With the recent changes in the turba library this patch has become obsolete. I aparently overlooked this for a while. So this is resolved.State ⇒ Assigned
Assigned to Gunnar Wrobel
Reopening and assigning to me as this is something I should try to solve for the 3.2 final release.State ⇒ Not A Bug
Okay, thanks for reminding me. So it basically makes no sense to try to fix this before Horde 4. Closing as not a bug.> The Kolab share driver ignores the initial id provided by the
> 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.
I know *nothing* about Kolab, so I can't comment on the underlying 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.
State ⇒ Unconfirmed
Summary ⇒ The Kolab share driver handling of share ids breaks creating shares in current Turba
Type ⇒ Bug
Priority ⇒ 1. Low
New Attachment: HK-GW-Fix_share_id_change.patch
Queue ⇒ Turba
The Kolab share driver ignores the initial id provided by the 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.