| Summary | Wrong multiple iCalendar events detection during SyncML |
| Queue | Kronolith |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | karsten (at) horde (dot) org |
| Requester | x3n (at) molinier (dot) eu |
| Created | 03/07/2007 (6730 days ago) |
| Due | |
| Updated | 04/27/2007 (6679 days ago) |
| Assigned | 04/01/2007 (6705 days ago) |
| Resolved | 04/27/2007 (6679 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
for you. Thanks.
State ⇒ Assigned
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Wrong multiple iCalendar events detection during SyncML
Queue ⇒ Kronolith
State ⇒ Unconfirmed
sent by the client. Is this analysis, the program checks if there is
on or more VEVENT element in the content.
If there are several element, Kronolith cannot handle it. So there is
an exception.
The bug is the following: we are not couting the number of VEVENT
element in VCALENDAR but the number of element in whole. There is a
problem when the client is sending a VTIMEZONE object at the same
time...
To solve this, I propose to leave away everything except VEVENT (we
don't care about VTIMEZONE here!):
-line 757 -
$components=array();
// Filtering components to keep only VEVENT objects
foreach($iCal->getComponents() as $component) {
if(is_a($component, 'Horde_iCalendar_vevent')) {
array_push($components, $component);
}
}
switch (count($components)) {
...
Best regards,
x3n
http://www.molinier.eu