Summary | Wrong eventduration with imported calendars |
Queue | Kronolith |
Queue Version | HEAD |
Type | Bug |
State | Resolved |
Priority | 2. Medium |
Owners | jan (at) horde (dot) org |
Requester | jrkuipers (at) lauwerscollege (dot) nl |
Created | 12/16/2006 (6795 days ago) |
Due | |
Updated | 04/19/2007 (6671 days ago) |
Assigned | 02/07/2007 (6742 days ago) |
Resolved | 04/19/2007 (6671 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | Yes |
Assigned to Jan Schneider
Taken from
State ⇒ Resolved
The US32Holidays.ics file has:
BEGIN:VEVENT
DTSTART;VALUE=DATE:20020218
DTEND;VALUE=DATE:20020219
SUMMARY:President's Day
UID:DA5629E3-0F90-4E6D-B7AE-0935905C6FDD
DTSTAMP:20050930T233908Z
SEQUENCE:5
RRULE:FREQ=YEARLY;INTERVAL=1;BYMONTH=2;BYDAY=3MO
END:VEVENT
Without the patch President's Day is a 2-day event.
ticket 4617Assigned to
New Attachment: Driver.php.diff
days. The calculated end date was increased by one day.
Also, when viewing events remotely (through webdav interface) in
Lightening, the end dates were shown one day too soon. [...]
kronolith/lib/Driver.php. Also, I think that it is wrong to subtract a
day from the end date when exporting an all-day event. I've attached a
patch that changes Driver.php accordingly.
There seems to be another bug in Driver.php. One of the comments says
that DTEND matches YYYYMMDDT2359(59|00), i.e. the second may be 59 or
00. But the code doesn't check whether the _minute_ is 59; instead
the code checks whether the _second_ is 59. This bug gets also fixed
by our patch.
backend. Importing Canadian Calendars made all full day events span
two days. The calculated end date was increased by one day.
Also, when viewing events remotely (through webdav interface) in
Lightening, the end dates were shown one day too soon. Thus, full day
events would show an error that the end date precedes the start date.
Reverting to 2.1.2 fixed the problem.
New Attachment: events.csv
New Attachment: events.ics
State ⇒ Feedback
Priority ⇒ 2. Medium
State ⇒ Unconfirmed
Queue ⇒ Kronolith
Summary ⇒ Wrong eventduration with imported calendars
Type ⇒ Bug
eventduration of multiday events is wrong. A negative number is
dispayed! When the begin- or enddate is changed and after that changed
back to the imported value the duration is calculated right.