Bug 326498 - google groups are not synced
Summary: google groups are not synced
Status: REPORTED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Google Resource (show other bugs)
Version: 4.11
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-23 12:28 UTC by Martin Tlustos
Modified: 2022-10-26 09:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Tlustos 2013-10-23 12:28:37 UTC
When adding (linking) a contact to a subgroup folder, it does not show up in the list nor gets synced with google contacts.

Reproducible: Always

Steps to Reproduce:
1. Open kontact/contacts
2. drag a contact from main google folder to subfolder/group
3. confirm "link contact"
Actual Results:  
nothing

Expected Results:  
the contact should show up in the group/show up twice when both main folder and subfolder are activated.
Comment 1 Martin Tlustos 2014-05-08 14:30:16 UTC
Still valid in version 4.13. Dragging a contact into a google subfolder/group does nothing. Should add the contact to the group instead.
Comment 2 Denis Kurz 2016-09-24 20:45:40 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 Martin Tlustos 2016-09-27 07:59:25 UTC
is still there in 5.1.3
Comment 4 Justin Zobel 2022-10-24 00:46:35 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Martin Tlustos 2022-10-26 09:06:39 UTC
As of now, the issue cannot be solved as the protocol has changed and the whole plugin doesn't work anymore, see bug 439285