[Tickets #12244] Re: edit event in CalDAV calendar does not work

[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/12244
------------------------------------------------------------------------------
  Ticket           | 12244
  Aktualisiert Von | lst_hoe02 at kwsoft.de
  Zusammenfassung  | edit event in CalDAV calendar does not work
  Warteschlange    | Kronolith
  Version          | 4.1.0beta1
  Typ              | Bug
  Status           | Feedback
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


lst_hoe02 at kwsoft.de (2013-05-24 11:10) hat geschrieben:

>> Cannot reproduce. Is this with all events? Only certain? Only old,
>> only new events?
>
> This code is hit, when one modifies an event.
>
> The problem is actually, that  
> $content->getAttribute('LAST-MODIFIED') returns an integer (seconds  
> since epoch), hence,  
> $content->getAttribute('LAST-MODIFIED')->before($modified) fires  
> that PHP error.
>
> $modified is a string in ISO-format.
>
> My workaround is to cast the integer into ISO-format for comparison,  
> if getAttribute('LAST-MODIFIED') returns an integer only.
>
> I posted my upgrade path on 15 May 2013 15:57:52 to the list with  
> subject "CalDAV change event fails with PHP error", maybe something  
> got screwed up then.

I can also confirm that the workaround fixes the update-event problem,  
but it looks like Lightning/CalDAV has some other flaws. The updated  
event is shown in Kronolith fine, but Thunderbird need a restart to  
actually show the changes done :-(