[Tickets #6949] Further Blackberry Funambol client issues

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/6949
-----------------------------------------------------------------------
  Ticket             | 6949
  Created By         | sblainey at chemop.org
  Summary            | Further Blackberry Funambol client issues
  Queue              | SyncML
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
-----------------------------------------------------------------------


sblainey at chemop.org (2008-06-18 07:43) wrote:

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.