[Tickets #10942] Horde_SyncMl_Device_Synthesis corrupts sync data

bugs at horde.org bugs at horde.org
Thu Jan 26 13:55:17 UTC 2012


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

Ticket URL: http://bugs.horde.org/ticket/10942
------------------------------------------------------------------------------
  Ticket             | 10942
  Created By         | fabio.bas at officineinformatiche.net
  Summary            | Horde_SyncMl_Device_Synthesis corrupts sync data
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             |
------------------------------------------------------------------------------


fabio.bas at officineinformatiche.net (2012-01-26 13:55) wrote:

Horde_SyncMl_Device_Synthesis is a class that provides functionality  
that is specific to the Synthesis.ch SyncML clients. The original  
class seems to have been writter just to workaround some old  
limitations for the windows mobile client:
- the inability to use DateTime in vTodo's DUE attribute, stripping  
off the Time part;
- the use of custom values in the PRIORITY attribute (1,2,3 instead of 0-9);

Using any recent synthesis syncml client (i tested the iphone and the  
android ones), these limitations doesn't exists anymore; but since  
they are forced anyway, the resulting vTodo gets corrupted:
- every vTodo's due date is changed to time 00:00;
- every vTodo's priority is changed to either 1,2,3;

I tried to comment out all of the class's methods, and syncs started  
working flawless.
Unfortunately i had no WindowsMobile or Palm devices to test this  
change with, but is suppose that since all the synthesis's products  
are based on the same library, the limitation is gone for all of these  
devices.







More information about the bugs mailing list