Tickets :: [#4438] Events longer than one day do not display correctly when they have recurrance

6.0.0-alpha10

5/15/25

Summary	Events longer than one day do not display correctly when they have recurrance
Queue	Kronolith
Queue Version	Git master
Type	Bug
State	Duplicate
Priority	1. Low
Owners
Requester	thorsten.schaub (at) debeka (dot) de
Created	09/20/2006 (6812 days ago)
Due
Updated	09/04/2015 (3541 days ago)
Assigned	11/09/2008 (6031 days ago)
Resolved	09/04/2015 (3541 days ago)
Milestone
Patch	No

09/04/2015 02:26:56 PM	Michael Rubinsky	Comment #7 State ⇒ Duplicate Version ⇒ Git master	Reply to this comment
Bug: 12488

12/14/2008 04:04:35 PM	Chuck Hagenbuch	State ⇒ Stalled

11/09/2008 10:01:21 AM	Jan Schneider	Comment #6	Reply to this comment
Not really, and I'd rather like to get rid of the duration completely, where possible. It's unreliable due to DST changes and leap years.

11/09/2008 02:28:44 AM	Chuck Hagenbuch	Comment #5 State ⇒ Feedback	Reply to this comment
Could we do something about this by storing the event's duration in the database, and using that to modify the time window we're looking at? I.e., event_start plus event_duration, or event_end minute event_duration?

04/13/2007 09:39:15 PM	Chuck Hagenbuch	Comment #4 State ⇒ Stalled	Reply to this comment
I'm going to stall this for now. Finding recurring events that span more than one day is just a hard problem, but hopefully not one that's going to bite many users.

10/12/2006 04:12:23 PM	Jan Schneider	Comment #3	Reply to this comment
The first part is fixed. I don't have any bright ideas about the other problem though.

09/20/2006 08:27:21 PM	Chuck Hagenbuch	Comment #2 State ⇒ Feedback	Reply to this comment
For some cases, taking the non-recur code from Kronolith::_getEvents() and applying it to recurring events as well should fix this. However, that's not going to catch cases where an event spans 2 days and you view only the 2nd day - recurrence calculation is based on day, so we simply wouldn't find the event in order to check it. And we'd theoretically need to look back before any given day however many days you can make an event span - which currently isn't limited. Would missing those events be acceptable? Anyone have a more clever idea?

09/20/2006 12:33:38 PM	thorsten (dot) schaub (at) debeka (dot) de	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Events longer than one day do not display correctly when they have recurrance Queue ⇒ Kronolith State ⇒ Unconfirmed	Reply to this comment
When adding an event that has different start and end dates and that also has a recurrance, only the first day is shown in day/week/month view. If no recurrance is set, the event shows on all days it occupies.