-
-
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
[Bug]: No calendar event email/notification when event content is updated #41084
Comments
Found the same issue in nextcloud/calendar#4428 |
…etween two events. Old comparison implementation compares each element of the array against each other with no respect for the associated array label, which leads to wrongful removals because one value is accidentally present in a completely different label. New comparision works 'by-label' individually. Refer to php manual https://www.php.net/manual/en/function.array-diff.php Partly fixes nextcloud#41084 because changes between 'SEQUENCE' not present, 'SEQUENCE:0' and 'SEQUENCE:1' were not detected in the old implementation and thus no email update sent. Plus formating fix. Signed-off-by: Robert C. Schaller <gtbc_robert.schaller@rsxc.de>
After some digging, I found that this a two part issue:
|
Nice! The array comparison fix would be a first step. Maybe that also fixes some other open bugs I have seen where users complained about receiving no update notifications. Regarding 2., you are right, the significantChanges list in ITip\Broker simply represents the fields strictly listed in the RFC and the overrule logic / sequence incrementing when changing other fields should be handled in Nextcloud and not in the upstream parsing library. How are you thinking about fixing this (asking purely out of interest)? I can help with testing. Cheers, Florian |
Signed-off-by: Robert C. Schaller <gtbc_robert.schaller@rsxc.de>
…tic significance evaluation fixes nextcloud#41084 , nextcloud/calendar#4428 , nextcloud/calendar#848 (presumably closed prematurely), nextcloud#5222 and nextcloud/calendar#5744 Signed-off-by: Robert C. Schaller <gtbc_robert.schaller@rsxc.de>
As trivial as this answer may sound, by implementing the (correct) overrule logic. It is (almost) all there already. Check out the Check out master...rcwschaller:nextcloud-server:fix/caldav/respect-event-organizers-increment-of-sequence I'll add a test for it and put it in a pull request when I find the time. BTW, good job finding even more open issues with probably the same cause. |
Ahh, I see! Thought it would be much more complicated to fix. That's very nice! |
Old comparison implementation compares each element of the array against each other with no respect for the associated array label, which leads to wrongful removals because one value is accidentally present in a completely different label. New comparison works 'by-label' individually. Partly fixes nextcloud#41084 because changes between 'SEQUENCE' not present, 'SEQUENCE:0' and 'SEQUENCE:1' were not detected in the old implementation and thus no email update sent. Co-authored-by: Christoph Wurst <ChristophWurst@users.noreply.github.com> Signed-off-by: Robert C. Schaller <gtbc_robert.schaller@rsxc.de>
Old comparison implementation compares each element of the array against each other with no respect for the associated array label, which leads to wrongful removals because one value is accidentally present in a completely different label. New comparison works 'by-label' individually. Partly fixes nextcloud#41084 because changes between 'SEQUENCE' not present, 'SEQUENCE:0' and 'SEQUENCE:1' were not detected in the old implementation and thus no email update sent. Co-authored-by: Christoph Wurst <ChristophWurst@users.noreply.github.com> Signed-off-by: Robert C. Schaller <gtbc_robert.schaller@rsxc.de>
Old comparison implementation compares each element of the array against each other with no respect for the associated array label, which leads to wrongful removals because one value is accidentally present in a completely different label. New comparison works 'by-label' individually. Partly fixes nextcloud#41084 because changes between 'SEQUENCE' not present, 'SEQUENCE:0' and 'SEQUENCE:1' were not detected in the old implementation and thus no email update sent. Co-authored-by: Christoph Wurst <ChristophWurst@users.noreply.github.com> Signed-off-by: Robert C. Schaller <gtbc_robert.schaller@rsxc.de>
Old comparison implementation compares each element of the array against each other with no respect for the associated array label, which leads to wrongful removals because one value is accidentally present in a completely different label. New comparison works 'by-label' individually. Partly fixes #41084 because changes between 'SEQUENCE' not present, 'SEQUENCE:0' and 'SEQUENCE:1' were not detected in the old implementation and thus no email update sent. Co-authored-by: Christoph Wurst <ChristophWurst@users.noreply.github.com> Signed-off-by: Robert C. Schaller <gtbc_robert.schaller@rsxc.de>
Old comparison implementation compares each element of the array against each other with no respect for the associated array label, which leads to wrongful removals because one value is accidentally present in a completely different label. New comparison works 'by-label' individually. Partly fixes #41084 because changes between 'SEQUENCE' not present, 'SEQUENCE:0' and 'SEQUENCE:1' were not detected in the old implementation and thus no email update sent. Co-authored-by: Christoph Wurst <ChristophWurst@users.noreply.github.com> Signed-off-by: Robert C. Schaller <gtbc_robert.schaller@rsxc.de>
Old comparison implementation compares each element of the array against each other with no respect for the associated array label, which leads to wrongful removals because one value is accidentally present in a completely different label. New comparison works 'by-label' individually. Partly fixes #41084 because changes between 'SEQUENCE' not present, 'SEQUENCE:0' and 'SEQUENCE:1' were not detected in the old implementation and thus no email update sent. Co-authored-by: Christoph Wurst <ChristophWurst@users.noreply.github.com> Signed-off-by: Robert C. Schaller <gtbc_robert.schaller@rsxc.de>
Please reopen this issue. As mentioned earlier #44017 is only part of the solution and I am still working on the second part. |
Bug description
When updating content fields of a calendar event (such as the summary, location, link, description, etc.), no email/notification with the updated event is sent to the event participants. As a user, I expect that participants of my event receive an email/notification, when I, e.g., change the location of the event, or when I update the link/url of an event that is supposed to be an online call.
The only way which works and where I can trigger an email/notification is when I update the date/time of the event (e.g. by making the event a minute longer), in addition to updating the content of the event. Another workaround is deleting the event and creating a new event with the updated content. However, this might confuse event participants, because they first receive an email/notification that the original event is cancelled.
Steps to reproduce
Expected behavior
Installation method
Community Docker image
Nextcloud Server version
27
Operating system
None
PHP engine version
None
Web server
Nginx
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: