[Tickets #7589] Re: itip: can't add event / shared calendar

bugs at horde.org bugs at horde.org
Sat Nov 1 18:48:05 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         | Chuck Hagenbuch <chuck at horde.org>
  Summary            | itip: can't add event / shared calendar
  Queue              | IMP
  Version            | HEAD
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2008-11-01 14:48) 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.

I know this will take some API methods that aren't currently there,  
and it probably pushes this from bug to enhancement, but I _think_  
that will keep things clear and make for a nicer user experience.





More information about the bugs mailing list