View Issue Details

IDProjectCategoryView StatusLast Update
0003882SOGoBackend Calendarpublic2017-09-28 12:52
Reporterremy Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Platform[Client] MicrosoftOSWindowsOS Version7
Product Version2.3.16 
Summary0003882: Can't dismiss missed reminders for recurring events or deleted event
Description

i use thunderbird with lightning, it is impossible to remove an event that was edited on a day belonging to recurrence. Other dates of this recurrence has not been edited can be deleted

Steps To Reproduce
  • Create a recurring event by inviting a participant with thunderbird
  • Subsequently edit the event on a day just by adding a description and confirm.
  • On the computer of the participant try to remove the event or deactivate the alarm, this is impossible.

the following error occurs when deleting the event:

MODIFICATION_FAILED

État : 2147500037, La requête ne peut pas être traitée.

Server Replied with 403

TagsNo tags attached.

Relationships

related to 0002561 resolvedludovic Can not invite to an exeption only 

Activities

ludovic

ludovic

2016-12-22 18:14

administrator   ~0011093

This is a Lightning issue - it sends the event without a sequence number.

If the participant opens the event and rather choses accept/decline/tentative, it'll work as expected.

I'm leaving the bug open since Lightning sends an EXDATE if you delete the particular recurrence-id instead of just setting the participant to a declined state. We are not handling that correctly in SOGo right now but this code is set to be refactored.

kodb

kodb

2017-01-02 18:39

reporter   ~0011162

I am experiencing the same issue but with the v2 web gui. I am unable to do anything with the endless series of reminders popping up. Is there a workaround for me to disable this and restart sogod?
Bob

francis

francis

2017-01-09 14:20

administrator   ~0011179

@kodb This is a different issue and it has been fixed (see 0003978).

remy

remy

2017-09-28 12:51

reporter   ~0012331

this problem occurs rather when the organizer edits its event (change of participant, date, place)

remy

remy

2017-09-28 12:52

reporter   ~0012332

the problem is still present in version 2.3.22

Issue History

Date Modified Username Field Change
2016-11-04 16:04 remy New Issue
2016-12-22 18:14 ludovic Note Added: 0011093
2016-12-22 18:14 ludovic Severity major => minor
2016-12-29 18:10 ludovic Relationship added related to 0002561
2017-01-02 18:39 kodb Note Added: 0011162
2017-01-09 14:20 francis Note Added: 0011179
2017-09-28 12:51 remy Note Added: 0012331
2017-09-28 12:52 remy Note Added: 0012332