Hi,

I'm facing a weird issue, and don't know where to put the blame.
When I create a webdav resource for my local owncloud (3.0) installation, and copy a contact (using kaddressbook) from one resource to the webdav one, it shows up correctly in owncloud, except if the source resource is the google resource (the new one : libkgoogle).
If it is copied from the google resource, the vcard is copied fine, but in the database the email address is set as name (and it is shown in the name list, and is unclickable).

Any thoughts on where to put the blame in all this?

Serafean

PS : the only difference I found between a copy from a vcard/facebook resource and the google resource is that the former have the FN field set, could that be the issue? (I know nothing about the vcard format, so bear with me please).

This could be a bug in the Akonadi Google resource. What happens if you try to copy from the Akonadi Google resource to another non-webdav resource?

The only writable non-webdav resource I have is a vcard directory, and everything works great there.

If I copy a contact with no email address, owncloud shows the contact as "unknown".

Not sure which party could be to blame here, but there is certainly some form of bad interaction going on.

Copying a contact from Google Contacts to the VCard resource works correct I gather?
If so, this could be a metadata interaction issue between the Google resource and Owncloud/WebDAV.

Read up a bit on the vcard specification, it seems that the FN field is mandatory, and the google resource somehow not setting correctly it might be the cause of the issue. It seems the vcard resource works around this by reading the N field. (who named these fields?)

Unfortunately I do not know whom named the fields, but I would recommend filing a bug against the Google Contacts resource on bugs.kde.org.

Done

Thanks