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

Search Results: 23 of 127 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

* Your Email Address
* Spam protection	Enter the letters below: . . __. . __ . . \| \|(__ \|/ `\| \| \|/\\|.__)\__\|\__.\|__\|
Comment	> On the Webpage an user has one own and four shared calendars and the > user's tasks. I see the data (pencil icon) of all calendars except > one. The latter shows "You are not allowed to see this calendar." A > CalDAV client queries the principal of an user and gets 6 shares, all > prefixes by <URL>rpc.php/calendars/<user>/ > > calendar:1 > calendar:2 > calendar:3 > calendar~4 > calendar~5 > tasks~6 > > Calemdars 1 and 2 are public ones, 3 and 5 and shared ones from > another user, 4 and 6 are ones from the user itself. > > All calendars except 5 are working as expected. The requests to > calendar 5 result in "500 Internal server error". A webdav client > shows the same. > > The calendar 5 has been accidently shared as "Object Creator x Show > x Read x Edit x Delete", everything else is unchecked, no user > configuered. > > The annoying thing here is the 500 http error code for the CalDAV > client, because it displays a warning each retry time. IMHO, if the > calendar is shared and visible to the user, the user should get > access to its metadata / container / whatever, but not necessarily to > the events, hence, neither the GUI nor CalDAV should get an error. > > Maybe related to bug #12380 .
Attachment
Watch this ticket