Bug 214790 - Data loss while syncing Google Contacts due to not supported multiple fields
Summary: Data loss while syncing Google Contacts due to not supported multiple fields
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: GoogleData Resource (show other bugs)
Version: unspecified
Platform: Gentoo Packages Unspecified
: NOR normal
Target Milestone: ---
Assignee: Adenilson Cavalcanti
URL:
Keywords:
: 242257 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-11-16 11:25 UTC by rubidon
Modified: 2017-01-07 22:15 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description rubidon 2009-11-16 11:25:58 UTC 
Version:           svn (using KDE 4.3.1)
Compiler:          4.3.4 
Installed from:    Gentoo Packages

When syncing the Akonadi ressource with google, the phone numbers of contacts wich have multiple phone numbers are not synced. As far as I understand it, this is because of missing features in libgcal. 
The real problem is, that when I sync the contacts again, ALL phone numbers of the above mentioned contacts are removed from my google contacts.
Perhaps it is possible not to sync phone numbers of contacts wich have multiple numbers or if thats not possible not to sync phone numbers at all.
Comment 1 Tobias Koenig 2010-08-03 14:16:42 UTC 
*** Bug 242257 has been marked as a duplicate of this bug. ***
Comment 2 Denis Kurz 2016-09-24 20:40:35 UTC 
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:15:14 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.