-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Calendars become read-only soon after their creation on BusyCal (BusyCal.app, 2022.1.4) #165
Comments
Xandikos doesn't do anything to day in terms of permissions management. What sort of responses do you see on the xandikos side? Can you attach the output of running xandikos with --dump-dav-xml? |
|
Interesting; I don't see anything here to suggest that xandikos is refusing write access. Is there anything on the client side that suggests the collection is read-only? Some clients (e.g. evolution) have a client-side setting to allow you to mark a collection as read-only. |
I have the same problem. Perhaps BusyCal goes read-only in response to detecting one of the unsupported properties? |
The reports of unsupported properties are for properties that BusyCal asks for but that Xandikos doesn't support. It's pretty common, and Xandikos just reports that those properties are not present. It may be that BusyCal relies on a particular property to be present (and storeable) to understand whether the calendar is read-only. None of the names of unsupported properties seem related to that though. |
After setting a quick server with
xandikos --defaults -d .
, I have added the CalDAV server to BusyCal. It loaded the default calendarcalendar
properly, I managed to create a new calendar, add an event and attach a file to it. A few seconds later however, all calendars becomeread-only
, and I couldn't make any change, from modifying an existing event, to making new ones.The text was updated successfully, but these errors were encountered: