[Tickets #14752] Recurring events can be created with broken recurrence end dates

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14752
------------------------------------------------------------------------------
  Ticket           | 14752
  Erstellt Von     | wahnes at uni-koeln.de
  Zusammenfassung  | Recurring events can be created with broken recurrence
                   | end dates
  Warteschlange    | Kronolith
  Version          | FRAMEWORK_5_2
  Typ              | Bug
  Status           | Unconfirmed
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


wahnes at uni-koeln.de (2017-12-14 15:47) hat geschrieben:

When creating a recurring event, e.g. one that is repeated every day,  
an erroneous record of that event is saved to the database if one  
clicks the "Stop at" radio button, does not enter any date but clicks  
on "Save". Upon clicking the Save button, an endless spinner appears.  
The same happens if one reloads the calendar page and tries to open  
the event in order to delete it. The erroneous event can only be  
corrected by editing it directly in the database.

Attached is a screenshot of an example event that causes this problem.
The data given there would be saved to the database as follows:

mysql> select * from kronolith_events where event_title='Go for a hike' \G
*************************** 1. row ***************************
                    event_id: RFyNlomOsDS3mAHc8CQ75Or
                   event_uid:  
20171214151839.j3DC241MiJzgf5Ma60GXF1J at foo.example.org
                 calendar_id: mmuster2
            event_creator_id: mmuster2
           event_description: asdf
              event_location: Somewhere over the rainbow
                event_status: 2
             event_attendees: a:0:{}
              event_keywords: NULL
            event_exceptions:
                 event_title: Go for a hike
             event_recurtype: 1
         event_recurinterval: 1
             event_recurdays: NULL
          event_recurenddate: 0000-00-00 00:00:00
            event_recurcount: NULL
                 event_start: 2018-02-14 00:00:00
                   event_end: 2018-02-22 00:00:00
                 event_alarm: 0
              event_modified: 1513261119
               event_private: 0
                event_allday: 1
         event_alarm_methods: a:0:{}
                   event_url:
                event_baseid:
event_exceptionoriginaldate: NULL
             event_resources: a:0:{}
              event_timezone:

Please note how the "event_recurenddate" column contains an invalid  
date, i.e. the date (if you consider "0000-00-00" to be a date) would  
be way before the event_start date.

Under some circumstances (I could not find out what those are exactly)  
a calendar with these kind of broken events also causes the CalDAV  
sync to fail. The CalDAV client would receive a HTTP "200" response  
instead of a normal "207" response (which would then contain  
individual "200" responses within the XML code in the response body,  
but not in the HTTP header).



wahnes at uni-koeln.de (2017-12-14 15:47) hat hochgeladen:  
kronolith-problem-recurring-event-with-no-end-date.png

https://bugs.horde.org/h/services/download/?app=whups&actionID=download_file&file=kronolith-problem-recurring-event-with-no-end-date.png&ticket=14752&fn=%2Fkronolith-problem-recurring-event-with-no-end-date.png