[Tickets #14510] Re: Lightning 4.7.4 can not update Events

[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/14510
------------------------------------------------------------------------------
  Ticket           | 14510
  Aktualisiert Von | Jan Schneider <jan at horde.org>
  Zusammenfassung  | Lightning 4.7.4 can not update Events
  Warteschlange    | Kronolith
  Version          | 4.2.18
  Typ              | Bug
-Status           | Unconfirmed
+Status           | Feedback
-Priorität        | 3. High
+Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2016-11-11 12:34) hat geschrieben:

> The following functions fail
> * Change appointments

The wire trace that you posted belows shows that the event title is  
actually changed though.

> * Delete notifications

> The error occurs in version 4 of Lightning.
>
> Seamonkey can handle the calendar without any problems.

What makes you think this is a Horde bug then? FWIW, I can update  
events with Lightning 4.7.4 just fine.

>
> Example:
>
> I change the Summary in '1' an save the event.

> CalDAV: recv:
> <d:multistatus><d:response><d:href>/horde3/rpc/calendars/testuser/calendar~FrK_wnAkETdEIeznjBkJFFe/8fcc8af9-b7d6-45af-8f17-f7bbf827956a.ics</d:href><d:propstat><d:prop><cal:calendar-data>BEGIN:VCALENDAR
> VERSION:2.0
> X-WR-CALNAME:Kalender von testuser
> PRODID:-//The Horde Project//Horde iCalendar Library//EN
> BEGIN:VEVENT
> DTSTART;TZID=Europe/Berlin:20161110T130000
> DTEND;TZID=Europe/Berlin:20161110T140000
> DTSTAMP:20161111T090339Z
> UID:8fcc8af9-b7d6-45af-8f17-f7bbf827956a
> SUMMARY:1

The SUMMARY has successfully changed.

> Why delete Horde 'X-MOZ-GENERATION:1'  and  'SEQUENCE:1' ?

Because Kronolith is not an iCalendar storage. It's a calendar server  
that converts to and from iCalendar instead.

> Thunderbird shows the old values.

Sounds like a Thunderbird problem to me then, unless proven otherwise.