Fri, 10 Apr 2026 02:21:37 +0000 https://bugs.horde.org/ticket/6949 Further Blackberry Funambol client issues Using the v6.06 Funambol Blackberry client After applying the fix suggested in defect 6939 for the RespURI issue I came across the following two issues: 1) Horde does not recognise the Blackberry Funambol client as the device id returned is 'fbb-xxx' rather than 'sc-pim-xxx' and the client id cannot be edited within the Blackberry edition of Funambol. The fix for this is to update the getDevice function within State.php to recognise 'fbb-' as a sync4j client. 2) Horde does not decode the base64 data provided by the Funambol client in the sync (interestingly enough, it does encode data it sends to the client). The fix for this is to update the convertClient2Server function within Device/Sync4j.php to call base64_decode to decode $content before calling sif2vcard. The above fixes allow me to sucessfully sync my Blackberry address book with Turba. I have not tried calendar, notes or todo as I do not use them. I can provide patches if required. Wed, 18 Jun 2008 11:43:13 +0000 https://bugs.horde.org/ticket/6949#t46634 Please provide the syncml log files from /tmp/syncml instead. Sun, 06 Jul 2008 17:26:05 +0000 https://bugs.horde.org/ticket/6949#t47279 Duplicate of bug #6995. Sun, 13 Jul 2008 09:17:17 +0000 https://bugs.horde.org/ticket/6949#t47486 > Duplicate of bug #6995. Only issue 1 is the same as bug 6995 - there is still the issue with Horde not decoding the base64 encoded data sent by the blackberry funambol. I have attached data.txt from /tmp/sync showing that the data sent by the client is not converted correctly. Mon, 14 Jul 2008 09:29:10 +0000 https://bugs.horde.org/ticket/6949#t47508 And here is a patch to allow Horde to sync data from the blackberry running Funambol. Mon, 14 Jul 2008 09:34:27 +0000 https://bugs.horde.org/ticket/6949#t47509 Please provide the client.xml log for that message too. Mon, 14 Jul 2008 10:23:19 +0000 https://bugs.horde.org/ticket/6949#t47510 > Please provide the client.xml log for that message too. Attached... Mon, 14 Jul 2008 10:35:01 +0000 https://bugs.horde.org/ticket/6949#t47511 >> Please provide the client.xml log for that message too. > > Attached... Just realised the client files are from a different session, so here is the corresponding data.txt Mon, 14 Jul 2008 10:38:00 +0000 https://bugs.horde.org/ticket/6949#t47512 Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/Sync.php?r1=1.59&r2=1.60&ty=u Mon, 22 Sep 2008 21:46:23 +0000 https://bugs.horde.org/ticket/6949#t49152 Please try the patch I just committed. Mon, 22 Sep 2008 21:46:28 +0000 https://bugs.horde.org/ticket/6949#t49153 Obviously this didn't fix it. See bug #6995 for a follow-up. Sat, 04 Apr 2009 12:56:49 +0000 https://bugs.horde.org/ticket/6949#t53510 Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/Sync.php?rt=horde&r1=1.62&r2=1.63&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/SyncElement.php?rt=horde&r1=1.17&r2=1.18&ty=u http://cvs.horde.org/diff.php/horde/docs/CHANGES?rt=horde&r1=1.1222&r2=1.1223&ty=u Sun, 05 Apr 2009 20:12:14 +0000 https://bugs.horde.org/ticket/6949#t53518 Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/framework/SyncML/SyncML.php?rt=horde&r1=1.21.10.18&r2=1.21.10.19&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Backend.php?rt=horde&r1=1.8.2.15&r2=1.8.2.16&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Backend/Horde.php?rt=horde&r1=1.8.2.16&r2=1.8.2.17&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Backend/Sql.php?rt=horde&r1=1.6.2.6&r2=1.6.2.7&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command.php?rt=horde&r1=1.4.10.12&r2=1.4.10.13&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/Alert.php?rt=horde&r1=1.18.10.15&r2=1.18.10.16&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/Final.php?rt=horde&r1=1.10.10.10&r2=1.10.10.11&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/Get.php?rt=horde&r1=1.14.10.15&r2=1.14.10.16&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/Map.php?rt=horde&r1=1.1.10.11&r2=1.1.10.12&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/Put.php?rt=horde&r1=1.12.10.12&r2=1.12.10.13&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/Sync.php?rt=horde&r1=1.17.10.17&r2=1.17.10.18&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Command/SyncElement.php?rt=horde&r1=1.3.2.9&r2=1.3.2.10&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/State.php?rt=horde&r1=1.17.2.17&r2=1.17.2.18&ty=u http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Sync.php?rt=horde&r1=1.8.4.20&r2=1.8.4.21&ty=u http://cvs.horde.org/co.php/framework/SyncML/tests/testpacket.php?rt=horde&r=1.2.2.1 http://cvs.horde.org/diff.php/horde/docs/CHANGES?rt=horde&r1=1.515.2.522&r2=1.515.2.523&ty=u Sun, 05 Apr 2009 20:24:45 +0000 https://bugs.horde.org/ticket/6949#t53521