[sync] FW: [Tickets #5148] Recurrence enddate not copied from latest Funambol WM plugin to kronolith

jochem at mondrian-it.nl jochem at mondrian-it.nl
Thu Mar 22 15:01:08 UTC 2007


I'd like to find and fix the problem here myself, so if anyone can just
point me in the right direction, I'd be happy to submit a patch.

Thanks,

Jochem

-----Oorspronkelijk bericht-----
Van: bugs at bugs.horde.org [mailto:bugs at bugs.horde.org] 
Verzonden: donderdag 22 maart 2007 15:01
Aan: bugs at lists.horde.org
Onderwerp: [Tickets #5148] Recurrence enddate not copied from latest
Funambol WM plugin to kronolith

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=5148
-----------------------------------------------------------------------
 Ticket             | 5148
 Created By         | jochem at mondrian.nl
 Summary            | Recurrence enddate not copied from latest Funambol WM
plugin to
                    | kronolith
 Queue              | SyncML
 Type               | Bug
 State              | Unconfirmed
 Priority           | 2. Medium
 Owners             | 
-----------------------------------------------------------------------


jochem at mondrian.nl (2007-03-22 07:00) wrote:

While testing the syncml interface to horde, I ran into the following
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'.





More information about the sync mailing list