opensuse 13.1 x86_64 kde 4.13.3 libkgap2-2 2.2.0-1.1 in kaddressbook i choose to display contacts using "inverted name" thus for any contacts we have <name> <nickname> and the list is orered by <name> and by <nickname> if i edit in google contacts a contact then after sync in kaddressbook for this contact we have <nickname> <name> thus the contact is moved at another place in the list Reproducible: Always Expected Results: respect the user custom view of the contacts list in kaddressbook
sorry it is kde 4.14.3
Created attachment 104801 [details] log when synchronizing kaddressbook and G contacts log when synchronizing kaddressbook and G contacts
yesterday thre aws an update of KDE Applications to 17.03. today i experiment there is no more sync problem from G contacts to kaddressbook. i wait for a week to confirm this.
kontact 5.10.2 libkgapi 18.12.2 problem still there
Where do you even configure the order in which names are displayed in KAddressbook, I can't actually find it. Can you check if the values are filled correctly on the Google side?
>> Where do you even configure the order in which names are displayed in >> KAddressbook, I can't actually find it. in "Contact" tab > Name > Display >> Can you check if the values are filled correctly on the Google side? yes Name and Nickname are correctly filled in G contacts just choose "reverse name" then you see contact changes its place and is displayed as "Name" "Nickname" then sync then again contact is displayed as "Nickname" "Name" and you get a goodie : photo disappears !
Other goodies : - "France" became "FR" ! -
I see - this is an attribute that is stored in the contact itself, very likely gets lost on next sync because Google doesn't support it. I'll see if we can be more clever about keeping local information during contact sync, only overwrite things that Google actually supports.
Also, let's keep this bug only about the name order, I saw the other reports about photo issues :) Please report the problem with the country separately.
also kaddressbook tags are deleted by sync.
i think generaly a contact item must be a merge of a kaddress contact item and a google contact item. this is a general rule for syncing. sync must not lead to lost.
The problem is that if we keep some data only locally because we cannot sync them to Google, it goes against the principle of Akonadi being only a cache and it can also lead to data loss - if you would delete your Akonadi database, you would lose all this information that we couldn't upload to Google. We should encode the custom fields that Google does not support out-of-the-box into some "extra" fields that we can sync to Google (but unfortunately no other clients will likely be able to understand them), and eventually have the feature where the Contact Editor would only allow changing fields that the respective backend supports (so if Google does not support Contact name ordering, we would simply not make it configurable when creating a new contact in Google Contacts addressbook). For now, I'll look into the first step - encoding everything into the extra fields.
kde plasma 5.15.5 kde framework 5.57.0 qt 5.12.3 kde app 19.04 No more problem. if i choose <name><nickname> then after sync it is still <name><nickname>