-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
CalDAV: Issue with write permissions and multiple shares #3677
Comments
I see two solutions here:
Just add |
I'd personally go with 2 for simplicity's sake. |
I'm already on it, I hate ordering, so will actually check it. But it's not complicated either. |
ok :) |
taken from nextcloud/calendar#316
Steps
Expected
test1 should be able to create events and see the calendar in the normal list.
Actually
test1 sees the calendar in the subscription list and therefor can not add events.
Workarounds
Swap step 4 and 5 makes it work. But you can then again break it, when you remove the "can edit" from all shares and add it to the first group again....
Dav response
The
{DAV:}write}
acl is set in https://github.com/nextcloud/server/blob/master/apps/dav/lib/CalDAV/Calendar.php#L123.That relies on
calendarInfo['{http://owncloud.org/ns}read-only']
. (https://github.com/nextcloud/server/blob/master/apps/dav/lib/CalDAV/Calendar.php#L275).The
read-only
property is set ingetCalendarsForUser
(https://github.com/nextcloud/server/blob/master/apps/dav/lib/CalDAV/CalDavBackend.php#L297),but only for the first calendar queried from the database (https://github.com/nextcloud/server/blob/master/apps/dav/lib/CalDAV/CalDavBackend.php#L304)
When sharing with group1 and group2 and only then giving write-permission to group1, group1 comes after group2 in the dav_shares table. Therefore that row is ignored.
The text was updated successfully, but these errors were encountered: