6.0.0-git
2018-12-15

[#8240] creator vs. organizer in kolab events / failure of setting events private
Summary creator vs. organizer in kolab events / failure of setting events private
Queue Kolab
Type Bug
State Assigned
Priority 1. Low
Owners wrobel (at) horde (dot) org
Requester m.gabriel (at) das-netzwerkteam (dot) de
Created 2009-05-04 (3512 days ago)
Due
Updated 2009-05-05 (3511 days ago)
Assigned 2009-05-05 (3511 days ago)
Resolved
Milestone
Patch Yes

History
2009-05-05 08:12:18 Jan Schneider Assigned to Gunnar Wrobel
State ⇒ Assigned
 
2009-05-04 18:02:40 m (dot) gabriel (at) das-netzwerkteam (dot) de Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Summary ⇒ creator vs. organizer in kolab events / failure of setting events private
Queue ⇒ Kolab
Milestone ⇒
Patch ⇒ Yes
New Attachment: 20090405_Kronolith_kolab_creator.patch Download
Reply to this comment
try the following (horde-webmail-1.2.3-rc1 with kolab backend):



   o let two users share their calendar share

   o let user A create an event with outlook/toltec

   o let user B create an event with outlook/toltec

   o let user A log into horde and view the created events

      -> for both events user A will be the owner

   o let user B log into horde and view the created events

      -> for both events user B will be the owner

   o expected behaviour: user A+B will see one event owned by user A

      and one event owned by user B

   o private events will fail also (user A can see details of user B's 
private events

      and vice versa)



backtrace:



   o toltec uses creator field, but no organizer field if not 
explicitly specified in outlook

   o horde (and also kontact as i read in [1]) use organizer field and 
horde maps it to creatorId.



attached you find a patch that fixed the issue for my scenario.



best,

mike



[1]

http://osdir.com/ml/kde.kolab.devel/2005-04/msg00073.html


Saved Queries