-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Unable to rename Contact birthday calendar #47330
Comments
This is still an issue, unfortunately, which would be great to have addressed. The inconsistency can bother some people between their calendars, especially if they use quick, short names [for their other calendars] like I do (eg. School, Work, Personal, etc.). |
Maybe the issue would be better titled with |
This comment was marked as resolved.
This comment was marked as resolved.
ixed it |
Still having the issue |
After some very light digging, it seems that the problem is on the server side, as I noticed no difference at all between the API calls and the results when trying to rename both normal calendars and the birthday calendar. Indeed, the problem is occuring after reloading the page, and the server is sending the older unchanged version. I didn't find much about the server on this repo, is this in the https://github.com/nextcloud/server repo ? (Sorry, really new to Nextcloud, I know this is a trivial question) |
Issue is not fixed, still unable to change the name and color. |
Indeed - the DB changes but the propfind for the user doesn't return the data that is there but a predefined string: server/apps/dav/lib/CalDAV/Calendar.php Lines 49 to 52 in 9d4b944
|
Steps to reproduce
Contact birthday
calendar.After refreshing the page, the changed name of the
Contact birthday
calendar returns to the original name and the user's avatar disappears (not shared). The calendar menu also changes fromUnshare from me
toDelete
.Calendar app
Calendar app version: (see apps admin page, e.g. 2.0.1)
2.2.0
Server configuration
Nextcloud Version: (see admin page, e.g. 17.0.2)
21.0.0
The text was updated successfully, but these errors were encountered: