View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002819SOGoWeb Calendarpublic2014-06-18 11:212016-09-23 19:34
Reporterams077 Assigned Toludovic  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Platform[Server] LinuxOSDebianOS Version7 (Wheezy)
Product Version2.2.5 
Summary0002819: SOGo allows you to set nonsense recurrence until date and event then fails to display at all
Description

When setting a repeat until date, SOGo doesn't prevent you from selecting a date that is earlier than the initial event.

When a recurring event has a 'repeat until' date that is earlier than the initial event date, the event fails to display at all in the calendar UI, and logs an error like this (I have anonymised the calendar name).

"""
Jun 17 12:37:02 sogod [28974]: [ERROR <0x2D3EECB0[SOGoAppointmentFolder]:${calendar_name}> missing exception record for recurrence-id 2014-06-13 00:00:00 +0000 (uid f2a8cec2-cf8c-4c6a-a89e-0d5e0941432f)
"""

Steps To Reproduce
  1. Create an event
  2. Select Repeat: Custom
  3. Customise the recurrence with Repeat = Daily, and Repeat Until = ${some date prior to the initial event}
  4. Save and close the event
  5. See the event is not displayed in the calendar.
Additional Information

It seems the event is created and stored. Event creation email notifications are sent, and the event (initial event only) is visible in Thunderbird+Lightning via CALDAV.

SOGo should do either or both of:

  1. Not allow a nonsensical 'repeat until' date in the first place
  2. Display the initial event even if the 'repeat until' date is nonsense. At least then a user can access the event to correct the 'repeat until' date.
TagsNo tags attached.

Activities

dgp

dgp

2014-07-11 11:48

reporter   ~0007315

We've just had a very similar issue, but this time from an externally generated invite (Exchange 2010). Or should this be raised as a new issue?

Recurrance-id's end date was set to before the start date:
DTSTART;TZID=GMT Standard Time:20140710T153000
RECURRENCE-ID;TZID=GMT Standard Time:20140709T164500

SOGo log contained:
Jul 11 12:29:35 sogod [2296]: [WARN] <0x82133760[SOGoAppointmentObject]:E12F51CAC3E24D778FA8E01A85724E9C0.ics> Invalid event: no end date; setting duration to PT1H

Removing the RECURRANCE-ID field allowed the single event to appear properly in the web interface.

Interestingly the event couldn't be deleted by Lightning. It was given a 403.
ludovic

ludovic

2016-09-23 19:34

administrator   ~0010678

You can no longer do this.

Issue History

Date Modified Username Field Change
2014-06-18 11:21 ams077 New Issue
2014-07-11 11:48 dgp Note Added: 0007315
2016-09-23 19:34 ludovic Note Added: 0010678
2016-09-23 19:34 ludovic Status new => resolved
2016-09-23 19:34 ludovic Resolution open => fixed
2016-09-23 19:34 ludovic Assigned To => ludovic