Summary | Recurring events overlapping days incorrectly shown |
Queue | Kronolith |
Queue Version | 4.1.2 |
Type | Bug |
State | Assigned |
Priority | 2. Medium |
Owners | Horde Developers (at) |
Requester | stefan (at) baer (dot) rwth-aachen (dot) de |
Created | 07/24/2013 (4312 days ago) |
Due | |
Updated | 09/04/2015 (3540 days ago) |
Assigned | 07/24/2013 (4312 days ago) |
Resolved | |
Milestone | 5 |
Patch | No |
Bug: 4438structure of the $results array to contain the event_id as part of the
data, and not as the key. This data structure , besides being used
everywhere within Kronolith, is also exported as-is from Kronolith's
API.
The problem here is that even when the logic to cover the dates
correctly is added, the $results array used to transport the calendar
data around can only support a single entry per day or each event id.
This will not be a simple fix.
Priority ⇒ 2. Medium
State ⇒ Assigned
Assigned to
Assigned to Michael Rubinsky
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Recurring events overlapping days incorrectly shown
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
recurring several days, the part of the event in the morning is not
displayed in the calendar:
Example: Event starts on 18 November on 5pm and ends on 19 November on
11am. Recurring every 1 day for 3 days, the event isn't visible on 19
November in the morning in the day, work week and week view. Only the
last morning part of the date on 21 November is visible in the view.
I've attached this example to this bug.