-
-
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
Birthday-calendar: properly handle deletion of addressbook #11305
Comments
GitMate.io thinks possibly related issues are #3003 (Disable birthday contacts calendar generation for user), #4451 ("Delete Calendar" Issue), #3759 (Contact delete tooltip), #410 (Birthday calendar not generated for shared contacts), and #9334 (Calendar of contact's birthdays are not editable after re-sync). |
Still existing in 18.0.0, using the following steps:
Reason: birthday-calender sync only iterates existing adressbooks (./apps/dav/lib/CalDAV/BirthdayService.php => function: syncUser) CC: @nickvergessen |
Hi, please update to 24.0.8 or better 25.0.2 and report back if it fixes the issue. Thank you! |
This issue still exists with NextCloud 26.0.2, Contacts 5.3.0 and Calendar 4.3.5. |
Hi, please open a new issue with up-to-date information. Thanks! |
Steps to reproduce
Remark: The following step is done because in my example i assume, that the entries into "Contacts_2" are more complete and more accurate!
are still there! No chance to remove the birthdays from the deleted "Contacts". If you
had double entries (one from "Contacts" the second from "Contacts_2" you will see two entries.
Remark: Birthdays can be removed then only if you delete the birthday-calendar, but in this case
you run into the new problem: Not being able to recreate any birthday-calendar (as a user)
Expected behaviour
With deleting "Contacts", the birthdays should be deleted as well, but the birthday-calendar should remain there!
Actual behaviour
With deleting "Contacts", all birthday-data is still in the birthday-calendar, and cannot be deleted.
Nextcloud version: 13.0.0
The text was updated successfully, but these errors were encountered: