nextcloud / nextcloud/calendar

Expire appointment confirmation link when appointment has been confirmed by attendee

Open
#5,689 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Steps to reproduce
  1. book an appointment
  2. confirm using the link in the email
  3. rechedule or delete the resulting calendar event
  4. open the confirmation link again
Expected behavior

The confirmation link should be marked as expired once processed for the first time.

Actual behaviour

A new event is created at the originally picked date and time, and notification emails are sent to both the host and the client.

Calendar app version

4.6.3

CalDAV-clients used

No response

Browser

No response

Client operating system

No response

Server operating system

armbian bullseye

Web server

None

Database engine version

None

PHP engine version

PHP 8.2

Nextcloud version

28.0.1

Updated from an older installed version or fresh install

Updated from an older version

List of activated apps

No response

Nextcloud configuration

No response

Web server error log

No response

Log file

No response

Browser log

No response

Additional info

No response

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 by reproducing the confirmation-link flow described in the issue, then trace the Calendar app code that handles the link after an attendee confirms an appointment. Done means reopening the original link is rejected as expired and does not recreate the event or send notification emails; no files or tests are named in the report.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.