Open Jerome-Herbinet opened 1 month ago
This is in fact by design. We thought about this when implementing the feature and mimicked what other calendaring clients do. E.g. Thunderbird accepts/declines a single recurrence by default and has a (somewhat hidden) button to accept all recurrences.
This is more of a feature request than a bug report.
This is in fact by design. We thought about this when implementing the feature and mimicked what other calendaring clients do. E.g. Thunderbird accepts/declines a single recurrence by default and has a (somewhat hidden) button to accept all recurrences.
This is more of a feature request than a bug report.
@st3iny thanks for your answer, but how can you explain that when clicking in invitation e-mails on the accept button (the Nextcloud styled HTML button in e-mail body), it accepts all recurrences at once ?
The invitation response buttons in the email actually use a completely different backend. They call a custom REST API made just for that purpose hence the behavior might be different.
But that is actually an interesting find. So there is a functional difference between both methods of accepting events which should not be the case.
Steps to reproduce
Easily tested on 2 test servers (Nextcloud 28 and 29) and a production server (Nextcloud 28).
Expected behavior
When one of the occurrences of the recurring event is accepted, all the others should be accepted.
Actual behaviour
Only one of the occurrences is marked as accepted, unlike the others.
Calendar app version
4.7.10 (and previous like 4.7.6)
CalDAV-clients used
Thunderbird and Tbsync
Browser
126.0.2
Client operating system
Ubuntu 22.04 LTS
Server operating system
CentOS
Web server
Nginx
Database engine version
MariaDB
PHP engine version
PHP 8.1
Nextcloud version
29.0.1 (and 28.0.5)
Updated from an older installed version or fresh install
Updated from an older version
List of activated apps
Nextcloud configuration
Web server error log
Log file
Browser log
Additional info
Can be provided if necesary