| Summary | Incorrect FreeBusy url when event covers many days |
| Queue | Kronolith |
| Queue Version | 2.3 |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | jan (at) horde (dot) org |
| Requester | patrick.abiven (at) apitech (dot) fr |
| Created | 12/17/2008 (6082 days ago) |
| Due | |
| Updated | 03/25/2009 (5984 days ago) |
| Assigned | 12/22/2008 (6077 days ago) |
| Resolved | 03/25/2009 (5984 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Taken from
State ⇒ Resolved
State ⇒ Assigned
Assigned to
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Incorrect FreeBusy url when event covers many days
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
When creating an event that covers many days (18 december 10AM to 20
december 10 AM), the Free Busy URL returned said that we are not
available the 18 december before 10 AM
(FREEBUSY:20081217T230000Z/20081220T225959Z).
In kronolith/lib/Kronolith.php, function _getEvents(), instead of
using $eventStart->mday and $eventEnd->mday for creating the events
(one for each day), shouldn't we use the index loop $i ?
Regards
Patrick