| 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 | 05/04/2009 (5854 days ago) |
| Due | |
| Updated | 04/20/2021 (1485 days ago) |
| Assigned | 05/05/2009 (5853 days ago) |
| Resolved | |
| Milestone | |
| Patch | Yes |
State ⇒ Assigned
Priority ⇒ 1. Low
New Attachment: 20090405_Kronolith_kolab_creator.patch
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Kolab
Summary ⇒ creator vs. organizer in kolab events / failure of setting events private
Type ⇒ Bug
State ⇒ Unconfirmed
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