| Summary | Recurrence enddate not copied from latest Funambol WM plugin to kronolith |
| Queue | Synchronization |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | jan (at) horde (dot) org |
| Requester | jochem (at) mondrian (dot) nl |
| Created | 03/22/2007 (6704 days ago) |
| Due | |
| Updated | 03/29/2007 (6697 days ago) |
| Assigned | 03/26/2007 (6700 days ago) |
| Resolved | 03/29/2007 (6697 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Assigned to Jan Schneider
Taken from Karsten Fourmont
State ⇒ Resolved
Assigned to Karsten Fourmont
New Attachment: Recurrence.patch
kronolith/lib/Recurrence.php
The function assumed the value of UNTIL is in the form of date('Ymd'),
while the funambol client supplies it as a unix timestamp. The
attached .patch will make the reverse assumption, that the value of
UNTIL is a timestamp if the function used is fromRRule20().
I've tested this, it fixes the bug.
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Recurrence enddate not copied from latest Funambol WM plugin to kronolith
Queue ⇒ Synchronization
State ⇒ Unconfirmed
problem. When the WM client defines an enddate for a recurrence item,
it is not correctly copied to the kronolith database. I've tracked the
enddate from the originally input SIF data, through the vCard that's
made of it.
The last point where I can easily track the data is where the
$backend->addEntry call is made in SyncML/Sync.php. The $content that
is fed to this function contains a RRULE line with the UNTIL key set
to the correct timestamp. Somewhere after this point, the enddate is
lost, as the resulting kronolith_events database entry contains the
enddate '9999-12-31 00:00:00'.