[Tickets #13822] Re: Shared calendar makes CalDAV fail with 500

[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/13822
------------------------------------------------------------------------------
  Ticket           | 13822
  Aktualisiert Von | Jan Schneider <jan at horde.org>
  Zusammenfassung  | Shared calendar makes CalDAV fail with 500
  Warteschlange    | Synchronization
  Version          | FRAMEWORK_5_2
  Typ              | Bug
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2016-01-28 13:11) hat geschrieben:

> created a 2nd calendar of an user, ticked all permissions for Object  
> Creator, but nothing else and tried to access it with a webdav client:
>
>  cadaver  
> 'https://127.0.0.1:443/horde/rpc.php/calendars/dvtest1/calendar~K-O2F29fNvZNnvyNhStU_w1/'
>
> Message from syslogd at msaj at Jan 27 20:54:32 ...
>  HORDE: [kronolith] Call to a member function toHash() on boolean  
> [pid 11253 on line 686 of  
> "/var/www/horde/kronolith/lib/Application.php"]

First of all, this is a CalDAV URL and not a valid WebDAV URL. And  
then it's exactly what happens if you still use an incorrect CalDAV  
URL from Kronolith versions earlier than 4.2.3. Are you sure this URL  
is from a recent Kronolith version?