kitserve / z-push-roundcube

Z-Push backend to allow synchronisation of Roundcube contacts with ActiveSync enabled mobile devices

z-push-roundcube

Z-Push backend to allow synchronisation of Roundcube contacts with ActiveSync enabled mobile devices

To use:

• Set up Z-Push as normal.
• Create the backend/roundcubecontacts directory
• Copy the file roundcubecontacts.php and config.php into the backend/roundcubecontacts folder.
• Open the main Z-Push config.php file in a text editor.
• Set BACKEND_PROVIDER to BackendRoundcubeContacts in the main config.php
• Update backend/roundcubecontacts/config.php and set Rouncube's DB and choose what mechanism you want to use to authenticate users (either database or imap)

z-push-roundcube's Issues

Non-ASCII characters get corrupted

Accented characters such as ö, â, é don't appear correctly in Roundcube if they were added on a mobile device (tested with Windows Phone). Seems to be an encoding conflict. Perhaps z-push-roundcube doesn't support UTF-8 correctly?

Not working

Hi your plugin not working with latest zpush 23.5 version account configuration not happening policy issue if i use BackendIMAP then its creating activesync account but if if select your Backend then its not creating account in phone please once again have a look in your code.

Incorrect phone # field types

I setup sync between my android phone and roundcube with z-push. It seems to work at first, but I noticed that when I enter a contacts mobile number in roundcube, on the phone it shows up incorrectly as their 'home' number. If I edit the contact on the phone, and change 'home' -> 'mobile', then in roundcube it changes incorrectly to 'other'.

As far as I can tell, the issue seems to be that z-push-roundcube doesn't know about the phone number type 'mobile' but only 'cell' per the v-card standard. But neither roundcube, nor android, nor activesync (or at least outlook) seem to call it 'cell', they all use 'mobile' so why follow the v-card standard?