nextcloud / nextcloud/calendar

error when deleting a user from a recurring event

Open
#8,513 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Steps to reproduce

1.Create a recurring event and invite a user to all the events. the user accepts
2. in the second event (or any other event except for the first one), delete the invited user
3. save the change to all events

Expected behavior

the user gets deleted from the event of which he was deleted from and all the events that come afterwards

Actual behavior

an error hapens that the event cannot be saved, and in the developer tools you can see that there was an 412 (precondition) error.

!Note.
i tested this again, and it seems the error hapens when the attendee accepts the invite and i remove him before it refreshes on my side.

Calendar app version

6.5.0

CalDAV-clients used

No response

Browser

No response

Client operating system

No response

Server operating system

No response

Web server

Apache

Database engine version

None

PHP engine version

None

Nextcloud version

No response

Updated from an older installed version or fresh install

None

List of activated apps

Nextcloud configuration

Web server error log

Log file

Browser log

Additional info

this is the error i see in Nextcloud

Image

this is the error i see in the dev tools

Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Calendar app's recurring-event attendee deletion flow and reproduce the reported steps: accept the invite, remove the attendee from a later event, and save changes to all events. Use the browser developer tools to inspect the 412 precondition response and compare behavior before and after the attendee acceptance refresh. Done means the attendee is removed from the selected event and all following events without a save error.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, full-stack
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.