Skip to content

Conversation

@naveensingh
Copy link
Member

@naveensingh naveensingh commented Oct 16, 2025

Type of change(s)

  • Bug fix
  • Feature / enhancement
  • Infrastructure / tooling (CI, build, deps, tests)
  • Documentation

What changed and why

The Nextcloud bug was originally caused by nextcloud/server#40876, fixed in nextcloud/server#44938, reverted in nextcloud/server#45547, and then fixed again in nextcloud/server#50784.

Tests performed

  • Saving and synchronizing attendees

Closes the following issue(s)

These problems aren't strictly caused by Fossify Calendar.

Checklist

  • I read the contribution guidelines.
  • I manually tested my changes on device/emulator (if applicable).
  • I updated the "Unreleased" section in CHANGELOG.md (if applicable).
  • I have self-reviewed my pull request (no typos, formatting errors, etc.).
  • All checks are passing.

@naveensingh naveensingh merged commit 8fe120e into main Oct 16, 2025
8 of 9 checks passed
@naveensingh naveensingh deleted the naveensingh/fix-cutype-unknown-in-servers branch October 16, 2025 11:41
fm-sys pushed a commit to fm-sys/MaterialCalendar that referenced this pull request Dec 2, 2025
* fix: set default relationship for attendees

* fix: set attendee type to required

* fix: set organizer even if it's missing from contacts

* docs: update changelog

Refs: FossifyOrg#818, FossifyOrg#135
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Event attendees are not saved to CalDAV account Calendar events which invited attendees don't execute e-mail notification

2 participants