Syncing is currently developer-level code - you need to be able to at least read logfiles! Testing is welcome; please report to the sync list (sync@lists.horde.org), but please keep in mind that the code is still in heavy development.
tail -f /tmp/horde.log | grep "SyncML:"
Synthesis client (v2.5.0.30) -> PDA -> USB serial cable -> Powerbook G4 running The Missing Sync (http://www.markspace.com/missingsync_palmos.php) -> Horde test installation
DO NOT USE THIS IN PRODUCTION!
If you're debugging and want to clean out data between sync attempts, you can try this set of commands if you use mysql (or adjust appropriately for other backends):
delete from kronolith_events where calendar_id='YOUR CALENDAR'; delete from horde_datatree where group_uid='syncml'; delete from horde_datatree_attributes using horde_datatree_attributes left join horde_datatree on horde_datatree_attributes.datatree_id=horde_datatree.datatree_id where horde_datatree.datatree_id IS NULL;
You can clear all session files (assuming the default backend) with rm -f /tmp/sess_*.
You'll have a lot of entries in the datatree with a group_uid of 'horde.history'. You will lose information from more than syncing by clearing them out, but you can do so. It is also useful to clear out horde.log and /tmp/sync to get a better feel for what is from the current sync attempt and what is not.
SyncMLDevicesFileFormats
SyncRoadMap
Syncing of date ranges as used by the Synthesis client is not yet supported. Please uncheck the "only from 30 days before until 90 days after today" checkbox.