-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add missing ACLs for deleted calendar objects to fix deletion #27343
Add missing ACLs for deleted calendar objects to fix deletion #27343
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a CS issue as well.
9cf8ff3
to
8451975
Compare
Due to a bug in Sabre it's necessary for calendar objects to implement ACLs. Otherwise the scheduling plugin will throw an error when it tries to fetch the owner of a calendar object that is being deleted. Ref sabre-io/dav#1345 Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
8451975
to
fc8daf5
Compare
return [ | ||
[ | ||
'privilege' => '{DAV:}read', // For queries | ||
'principal' => $this->getOwner(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a difference between returning the actual owner principal URI and {DAV:}owner
? If the former is required, might as well put it everywhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no difference right now. There might be one once we allow the trash bin access for shared calendars
Due to a bug in Sabre it's necessary for calendar objects to implement
ACLs. Otherwise the scheduling plugin will throw an error when it tries
to fetch the owner of a calendar object that is being deleted.
Ref sabre-io/dav#1345
Required for nextcloud/calendar#3129