Bug 336494 - Broken CardDAV sync with Virtuoso ODS address book
Summary: Broken CardDAV sync with Virtuoso ODS address book
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: DAV Resource (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-20 12:54 UTC by cordawyn
Modified: 2017-01-07 22:49 UTC (History)
2 users (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 cordawyn 2014-06-20 12:54:27 UTC
I've set up Virtuoso ODS to provide address book via CardDAV ("virtuoso-opensource" and "virtuoso-vad-ods" packages, version 6.1.6). When I create/edit/delete a contact in kaddressbook ("Contacts" component of Kontact), it is properly synchronized with Virtuoso. However, if a contact is created in Virtuoso, it is not synchronized with kaddressbook (won't appear in the list of contacts). If I edit a contact coming from kaddressbook using the web interface of Virtuoso, it disappears in the contact list of kaddressbook on the next sync.

I presume, kaddressbook adds some metadata to the contacts to help it with sync'ing, but Virtuoso overwrites/wipes it on updates and kaddressbook becomes unable to track them?

Reproducible: Always

Steps to Reproduce:
1. Setup Virtuoso ODS and a "Local CardDAV" in kaddressbook to sync contacts with it (setup details are in "Additional Information" section below).
2. Login to Virtuoso ODS web UI, navigate to "AddressBook", add a contact.
3. Update Address Book folder in kaddressbook - the contact created in Virtuoso does not appear in the list.
4. Add a contact in kaddressbook, visit Virtuoso ODS web UI, Address Book. The contact appears in the list of contacts.
5. Edit the contact in Virtuoso ODS web UI, save changes.
6. Refresh the list of contacts in kaddressbook - the contacts disappears from the list.
Actual Results:  
The contacts created or updated in Virtuoso ODS are not sync'ed with kaddressbook. They just disappear from the list of contacts in kaddressbook (but still remain in Virtuoso ODS).

Expected Results:  
Contacts created in Virtuoso ODS address book should appear in kaddressbook on sync.
Contacts updated in Virtuoso ODS address book should not disappear from kaddressbook.

Virtuoso:
- Install 2 packages "virtuoso-opensource" and "virtuoso-vad-ods".
- (Optional) Make sure "AddressBook" VAD package is installed by visiting Virtuoso Conductor web UI at http://localhost:8890/ > "Conductor" > login using "dba / dba" admin credentials > "System Admin" > "Packages".
- Create an ODS user in "System Admin" > "User Accounts". Make sure "User type" is set to "WebDAV". Note "DAV home page" setting, you'll need it later.

KAddressBook:
- Add Address Book, "DAV Groupware Resource"
- Enter user credentials from Virtuoso ODS user.
- Pick "Configure the resource manually".
- Click "Add", pick "CardDAV", use "http://127.0.0.1:8890/#{ODS_HOME_DIR}/addressbooks/" for "Remote URL", where ODS_HOME_DIR is "DAV home page" string from above. My complete path looks like "http://127.0.0.1:8890/DAV/home/cordawyn/addressbooks/".
- Click "Fetch", pick the only entry from the list below, click "OK".
Comment 1 cordawyn 2014-06-20 13:13:42 UTC
Added a reference to the bug report at the OpenLink forum: http://boards.openlinksw.com/support/viewtopic.php?f=17&t=6328&start=0
Comment 2 Grégory Oestreicher 2014-10-05 09:42:00 UTC
Is this bug still present in 4.14.1?

Cheers,
Grégory
Comment 3 cordawyn 2014-10-12 09:41:51 UTC
I'll let you know when I get my hands on the update (I'm using 4.13.3).
Comment 4 Denis Kurz 2016-09-24 20:45:17 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 5 Denis Kurz 2017-01-07 22:49:44 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.