-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please implement support of IM fields #46
Comments
I've looked into this (and still am). The trouble is: there's multiple ways to implement this:
In the end, there's probably no "nice" way to do this. |
I have pushed a branch issue_46 which tries to implement instant messenger types. |
Thank you. I also use CardDAV-Sync. For now it seems all data displayed correctly except "custom titles". |
What do you mean by "custom titles"? |
Here is screenshots. |
Not sure where "Home" comes from, but roundcube doesn't support "Google Talk" as an option. |
Yes, these titles/labels comes from CardDAV-Sync client, but Roundcube displays them correctly in the "Phone" section although RC itself does not support such titles/labels in adding/editing interface.
For some reason all Here is screenshots from my smartphone: |
The Plugin supports custom labels via the X-AB-LABEL extension. New Labels cannot be created in roundcube but once a custom label has been seen it is available for selection. I guess the same extension is used for instant messenger properties and it should be straightforward to extend the use of the custom label support for those properties. |
Implemented on v4.1. It's difficult to achieve interoperability with other clients, but I tried to make it as good as possible. See doc/devdoc/IMPP.md for some details. |
Hi
Currently carddav plugin does not show IM data (Jabber, ICQ, ...) in "Contact properties" for contacts that already have such fields. And there is no "IM" option under "Add field..." menu in "Add new contact" while in default adressbook "Personal Addresses" we can add IM fields.
The text was updated successfully, but these errors were encountered: