[Tickets #11976] Re: invation emails are handled wrong

[noreply at bugs.horde.org]

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

Ticket-URL: http://bugs.horde.org/ticket/11976
------------------------------------------------------------------------------
  Ticket           | 11976
  Aktualisiert Von | jmozdzen at nde.ag
  Zusammenfassung  | invation emails are handled wrong
  Warteschlange    | Kronolith
  Version          | 4.0.3
  Typ              | Bug
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


jmozdzen at nde.ag (2013-02-16 13:21) hat geschrieben:

After updating to the lastest PEAR code, things still don't work for  
me. (As expected - I just wanted to verify & report back)

- create single-day event, myself as invitee. Kolab/IMAP backend  
calendar entry has only start-date entry
- open email: gets displayed properly, due to below's cosmetic fix
- accept email: Kolab/IMAP backend calendar entry changes to  
start-date, end-date (end date set to start date +1)
- even after logoff/logon, kronolith still shows the calendar view  
entry as single-day. If I open the event, it does however show the  
changed end date.
- Logoff, erasing the cache, logon, shows the event as two-day event  
in kronolith's calendar view. Horde caching sucks.

Initation handling still seems broken, as accepting the invitation  
does not adjust the end date according to the differences between  
invitation and storage semantics for "end-date" and thus wrongly  
modifies calendar entries. To me, this is a severe error.