Tickets :: [#678] Not usable share Calendar with Kolab backend

6.0.0-beta1

11/5/25

Summary	Not usable share Calendar with Kolab backend
Queue	Kronolith
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	1. Low
Owners	stuart (at)
Requester	charly (at) aquiline (dot) es
Created	10/08/2004 (7698 days ago)
Due
Updated	03/31/2005 (7524 days ago)
Assigned	03/15/2005 (7540 days ago)
Resolved	03/31/2005 (7524 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

03/31/2005 01:20:33 PM	stuart	Comment #9 State ⇒ Resolved	Reply to this comment
No problems and several success stories reported, so I'm taking this as resolved.

03/15/2005 03:38:19 PM	stuart	Comment #8 State ⇒ Feedback	Reply to this comment
I've just committed the patch: http://cvs.horde.org/diff.php/framework/Kolab/Kolab.php?r1=1.30&r2=1.31&ty=u which I believe resolves this issue. At least, it does so on my development setup. Testing is now needed to ensure that it is correctly resolved, and perhaps we can finally close this ticket!

02/17/2005 03:41:25 PM	dsandras (at) seconix (dot) com	Comment #7	Reply to this comment
Any news about this? Could you make your patches public so that others can test? Thanks.

02/06/2005 09:33:19 AM	matt (at) fruitsalad (dot) org	Comment #6	Reply to this comment
This is fixed now in my local installation, I believe Stuart are reviewing patches for incorporation into Horde CVS

10/15/2004 10:08:49 AM	charly (at) aquiline (dot) es	Comment #5 New Attachment: Kolab.php	Reply to this comment
I'm unable to share resources. I send my modified Kolab driver (framework). My scenario: - two users (there are other but not worry about): - first user set a share Memo giving second all perm to it (vía list Notepads). When second user login can only see the Notepad from first. I think the problem is that this code can't set corretly shares resources. In line 1440 we get the shares but second get none. Then in line 1533 (comented out code) the resource don't exist in the $remote_shares (but exist in the shares) Another issue is about domain. When we log into imap using the manager acount, we need to provides the @<domain> (I put it manualy) to find out folders (line 1519). I'm lost. Please help. Thanks.

10/15/2004 01:15:39 AM	Chuck Hagenbuch	Comment #4	Reply to this comment
So, Stuart, is this resolved now?

10/14/2004 09:18:12 PM	stuart	Comment #3	Reply to this comment
You're right about the value.priv setting. I've changed it to use value.shared instead now, so using shared resources should work.

10/14/2004 05:08:04 PM	charly (at) aquiline (dot) es	Comment #2	Reply to this comment
It not posible to share any resource (task/notes/calendar) whith the kolab Backend. I think the problem is in the framework/Kolab/Kolab.php. The _syncShares method can't handle correctly shared resouces due to shared uid is value.priv (folder annotation) and is only accesible from the creator. Can you give me some ideas to get share resources working with Kolab? Thanks.

10/08/2004 11:21:30 AM	Jan Schneider	Assigned to stuart State ⇒ Assigned

10/08/2004 10:28:05 AM	charly (at) aquiline (dot) es	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Not usable share Calendar with Kolab backend Queue ⇒ Kronolith State ⇒ Unconfirmed	Reply to this comment
When creating new share Calendar, with Kolab backend, others user can't acces this resource. And after that whe get blank screen accesing Kronolith. The problen is near the synchroniseShares (Kolab.php), the driver don't know where to find the share folder (imap) for the share Calendar and think is local to the user, getting to a bad situation in the datatree. To get a working Kronolith is necesary to delete the share from the datatree and the share folder (imap). Sorry for my english.