Open rumxxx opened 7 years ago
cc @rullzer @georgehrke
I am having the same issue.
The server responded with an error.
The request for account “xxx” failed.
The server responded with“501”to operation CalDAVUpdateShareesQueuableOperation.
requires us to change from our own sharing implementation to Sabre/DAV's. Will have to evaluate how complex that's gonna be.
I am having the same issue.
Der Server meldet Fehler Die Anfrage für „Account „XXX““ ist fehlgeschlagen.
Antwort des Servers „501“ an Vorgang CalDAVUpdateShareesQueuableOperation.
@BKapelari Please use the Github Reactions feature instead of commenting +1, 👍 etc. These kinds of comments just unnecessarily notify everyone subscribed to this issue. Thx! :)
This issue has been automatically marked as stale because it has not had recent activity and it seems to be missing some essential informations. It will be closed if no further activity occurs. Thank you for your contributions.
Do you still want to implement this? If no, please close this issue. Thanks!
@szaimen Yes, please.
So I suppose calendar sharing still doesn't work with the macOS calendar and NC21.0.2?
Also see https://github.com/nextcloud/server/issues/26668 for a related ticket about how sharing is handled now vs how it could be handled instead.
Just adding some detail from my testing: this issue is particularly disrupting, as the error posted above by @Inseeker seems to persists even after unsharing the calendar or restarting Calendar.app.
As soon as a calendar gets shared using the built-in dialog in Calendar.app there's no way to get rid of the warning sign in the sidebar nor of the error messages popping up at regular intervals. You're pretty much stuck with a broken calendar.
EDIT: Unsharing the calendar and deactivating and reactivating the CalDAV account in the settings seems to make the error messages go away. Still, this is sadly not viable for production in a site using Calendar.app as main CalDAV client.
Very much looking forward to see some support implemented (or at least some more gracious error handling).
It really leaves a bad taste that fixing existing bugs seems to have a much lower priority than introducing new features with each release. We would pretty much appreciate the opposite order!
Currently, trying to share a calendar using the MacOS Calendar.app produce the following error:
"user":"ncadmin","app":"webdav","method":"POST","url":"\/remote.php\/dav\/calendars\/ncadmin\/3F283E41-2239-452D-BE13-382E6CBB282F\/","message":"Exception: {\"Message\":\"HTTP\\/1.1 501 There was no plugin in the system that was willing to handle this POST method.\",\"Exception\":\"Sabre\\DAV\\Exception\\NotImplemented\",\"Code\":0,\"Trace\":\"#0 \\/var\\/www\\/nc12\\/3rdparty\\/sabre\\/dav\\/lib\\/DAV\\/Server.php(254): Sabre\\DAV\\Server->invokeMethod(Object(Sabre\\HTTP\\Request), Object(Sabre\\HTTP\\Response))\n#1 \\/var\\/www\\/nc12\\/apps\\/dav\\/lib\\/Server.php(253): Sabre\\DAV\\Server->exec()\n#2 \\/var\\/www\\/nc12\\/apps\\/dav\\/appinfo\\/v2\\/remote.php(33): OCA\\DAV\\Server->exec()\n#3 \\/var\\/www\\/nc12\\/remote.php(162): require_once('\\/var\\/www\\/nc12\\/a...')\n#4 {main}\",\"File\":\"\\/var\\/www\\/nc12\\/3rdparty\\/sabre\\/dav\\/lib\\/DAV\\/Server.php\",\"Line\":487,\"User\":\"ncadmin\"}","userAgent":"Mac+OS+X\/10.12.5 (16F73) CalendarAgent\/386","version":"12.0.0.29"}
SabreDAV already support this->http://sabre.io/blog/2016/sharing-changes/ and would be nice to see this implemented into NC.