[Tickets #7589] Re: itip: can't add event / shared calendar
bugs at horde.org
bugs at horde.org
Mon Nov 3 09:07:15 UTC 2008
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/7589
------------------------------------------------------------------------------
Ticket | 7589
Updated By | rsalmon at mbpgroup.com
Summary | itip: can't add event / shared calendar
Queue | IMP
Version | HEAD
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
rsalmon at mbpgroup.com (2008-11-03 04:07) wrote:
> Okay. The fact is that unless we simply switch them off, users are
> going to use invitations in a shared calendaring environment, so I
> think we ought to make this smoother. Saying it's a user education
> issue is fair, but I think the software needs to do some of that
> education; this is a pretty unintuitive error to push off on admins.
>
> So: stepping back a bit, I think we should detect whether the event
> is already on a calendar that the user has access to. We should also
> check the permissions the user has to the event. That way we can
> offer a list of context-specific actions that we know should be
> possible:
>
> - add this to my calendar (it's not there already)
> - update this on my calendar (it's there on a calendar i own)
> - create a copy on my calendar (i can see it on someone's calendar,
> but not write to it)
> - etc.
Another way around could be (and I don't know if it is the right way to go) :
- if a user owns (or has access to) more than one calendar, then add a
combo box to the itip driver which contains a list of calendars that
the user can update ( and read ?). The selected calendar will be the
user's default calendar.
More information about the bugs
mailing list