[Tickets #13664] Re: accept event to Horde CalDAV calendar from Thunderbird Lightning parses Attendees

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/13664
------------------------------------------------------------------------------
  Ticket           | 13664
  Aktualisiert Von | kevin at kevin-online.com <kevin at kevin-online.com>
  Zusammenfassung  | accept event to Horde CalDAV calendar from Thunderbird
                   | Lightning parses Attendees
  Warteschlange    | Kronolith
  Version          | 4.2.2
  Typ              | Bug
  Status           | Duplicate
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


willem.verbruggen at anagky.be (2014-11-05 10:21) hat geschrieben:

> Basically a duplicate of request #3965, please add your information  
> there. See also request #13027.

We saw 3965 before and it is related: still the error is the parsing  
of the attendees thereby creating a meeting in your calendar with  
seemingly a wrong organizer.  BUT when doing the same from IMP, it  
works the same way with yourself also as organizer with the difference  
that there are no attendees .  So an enhancement to set the correct  
organizer is another step  forward (and as we saw in the code and the  
icalendar RFC an elaborate one) but not the problem here as IMP works  
the same way regarding organizer.  So for me this is not a duplicate.

Request 13027 has state resolved?
The parsing of attendees works correctly when creating new items via  
CalDAV from Lightning and has to keep on working this way.  Still  
there is a need NOT to parse the attendees when we are only accepting  
an externally received invite which we still want to take time in our  
own calendar after accepting.  This will have to be coded per client  
as I am not aware of a header/standard in the RFC that the clients  
might use.  Disclaimer: I am not a specialist in this icalendar RFC.