Backslash in SORT-STRING

I use the em-Client for my contacts under Windows. Some contacts get an \ added in the SORT-STRING field. I use “last name”, “first name” in the SORT-STRING field. The \ is added in front of the comma and when you save again, you get another .

I sync my contacts to my ownCloud (version 6.0.2) via cardDAV. Never had this problem with Thunderbird.

E.g.:

BEGIN:VCARD
VERSION:3.0
UID:26643617-9623-440f-85ee-e4b736175822
N:Mustermann;Mark;;;
SORT-STRING:Mustermann\, Mark
FN:Mark Mustermann
REV:2014-02-18T13:31:36+00:00
PRODID:-//eM Client/6.0.19872.0
END:VCARD

Hi,
sorry for the late reply, is this issue still occurring?
What version of eM Client are you using?

Thank you,
Paul.

Hi!

Im using Version 6.0.19861.0

THX
themmm

Hi,
we’ve come across this issue before, but it’s actually an issue with owncloud.
The issue should be fixed in next release of owncloud hopefully.

Thank you for understanding,
Paul.

Hello themmm,

I get the same issue. In owncloud 6.0.3 it is still not fixed.
I use eM Client 6.0.20498.0

Harald

I opend an issue und github issuetracker
https://github.com/owncloud/contacts/issues/512
Maybe it’s an error from the eM client?

Harald

Hi Harald, no this is unfortunately an issue with owncloud, I suggest contacting their support in order to resolve it.

Thank you for understanding,
Paul.

I don’t think so. With other cardav clients it’s working well. But from eM is (probably) every comma backslashed - for example in Organization field.

Example:

vcard from owncloud (v5):

BEGIN:VCARDVERSION:3.0
UID:c73bbb7a-359c-4902-abc7-0d3c0a6a55d9
N:Vomáčka;Pepa;;;
SORT-STRING:Vomáčka Pepa
FN:Pepa Vomáčka
REV:2014-07-06T23:23:36+00:00
ORG:Org, ltd.
TITLE:řidič, závozník
TEL;TYPE=WORK;TYPE=VOICE;TYPE=PREF:+420774666777
PRODID:-//eM Client/6.0.20498.0
TEL;TYPE=HOME:+420606666888
ADR;TYPE=HOME:;;Masarykova, 600;;;;
END:VCARD

In this state, eM show it right. Without backslashes (i see backslashs only in source of vcard). Everything fine.

In eM I edit this contact - update field NOTE and save.

In owncloud I see this:

BEGIN:VCARDVERSION:3.0
UID:c73bbb7a-359c-4902-abc7-0d3c0a6a55d9
N:Vomáčka;Pepa;;;
SORT-STRING:Vomáčka Pepa
FN:Pepa Vomáčka
REV:2014-07-06T23:27:34+00:00
ORG:Org\,  ltd.;
TITLE:řidič, závozník
TEL;TYPE=HOME;TYPE=VOICE:+420606666888
TEL;TYPE=WORK;TYPE=VOICE;TYPE=PREF:+420774666777
ADR;TYPE=HOME:;;Masarykova, 600;;;;
NOTE:pozn
PRODID:-//eM Client/6.0.20498.0
END:VCARD

Result: duplicate backslash in some fields. I found two in this moment - ORG and SORT-STRING (may be FN too).


It’s only one  BUG I found in this software … I am quite satisfied, for now. :slight_smile:

I’m sorry … I looking log file and I found probably error in owncloud (as you said).

eM putting only one backslash:

01:27:25.602|015|   C: PutCommand [https://](https://...)...
01:27:25.602|015|   BEGIN:VCARD
01:27:25.602|015|   VERSION:3.0
01:27:25.602|015|   UID:c73bbb7a-359c-4902-abc7-0d3c0a6a55d9
01:27:25.602|015|   N:Vomáčka;Pepa;;;
01:27:25.602|015|   SORT-STRING:Vomáčka Pepa
01:27:25.602|015|   FN:Pepa Vomáčka
01:27:25.602|015|   REV:2014-07-06T23:23:36+00:00
01:27:25.602|015|   ORG:Org\,  ltd.;
01:27:25.602|015|   TITLE:řidič\, závozník
01:27:25.602|015|   TEL;TYPE=HOME,VOICE:+420606666888
01:27:25.602|015|   TEL;TYPE=WORK,VOICE,PREF:+420774666777
01:27:25.602|015|   ADR;TYPE=HOME:;;Masarykova\, 600;;;;
01:27:25.602|015|   NOTE:pozn
01:27:25.602|015|   PRODID:-//eM Client/6.0.20498.0
01:27:25.602|015|   END:VCARD

But read two backslashes:

01:30:25.424|015| Content:<?xml version="1.0" encoding="utf-8"?><multistatus xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns" xmlns:card="urn:ietf:params:xml:ns:carddav"><response><href>/owncloud/remote.php/carddav/addressbooks/test/contacts/99a5d801-72db-4434-b39a-9f6d69ed9865.vcf</href><propstat><prop><address-data>BEGIN:VCARD
VERSION:3.0
UID:c73bbb7a-359c-4902-abc7-0d3c0a6a55d9
N:Vomáčka;Pepa;;;
SORT-STRING:Vomáčka Pepa
FN:Pepa Vomáčka
REV:2014-07-06T23:27:34+00:00
ORG:Org\, ltd.;
TITLE:řidič\, závozník
TEL;TYPE=HOME;TYPE=VOICE:+420606666888
TEL;TYPE=WORK;TYPE=VOICE;TYPE=PREF:+420774666777
ADR;TYPE=HOME:;;Masarykova\, 600;;;;
NOTE:pozn
PRODID:-//eM Client/6.0.20498.0
END:VCARD
</address-data><getetag>"660c2d000b4151bcfac901fcce42dd15"</getetag></prop><status>HTTP/1.1 200 OK</status></propstat></response></multistatus>

This is bad … ownCloud not fix it yet even in version 6. And I also can not upgrade from version 5.

Workaround in eM have been very useful. Please, please … Thanks.

I cannot save this log properly :frowning: In “ORG:Org” is two backlashed (in second part)…

Hi Martin, as you mentioned yourself, the issue is really held within Owncloud, the issue has been reported and we’re still waiting for a fix, unfortunately that’s all we can do at the moment, it might help if you report the issue yourself as well. The more the better.

Sorry for the inconvenience,
Paul.

Hello,

this issue is still not fixed in em 6.0.21040 and OwnCloud 7.02. Never had problems with any other OC CardDav clients. EM seems to trash slowly my cardav entries on the server ebcause I hardly have a chance to alter some card entries in em: almost everytime an error occurs saying that the server doesn’t support this or that feature. Even if only altering a typo in the name… Seems em is not capable of talking with owncloud card service at all in a usable manner…? As I said: no other client does have these problems (TB, CardDav(Android), Webclient)
Is there a cance this will be fixed in near future? I’m in test phase, thinking about changing a bunch of installation from TB to EM…

Hi, I’m sorry this issue is causing issues while using eM Client with OwnCloud, but just as I previously stated, this is unfortunately an OwnCloud issue, that has been reported several times, we believe the best solution for this issue is to report the issue to OwnCloud so the synchronization can work properly with all CardDAV clients without the need to workaround the issue.

Thank you for understanding,
Paul. 

The issue is still open in ownCloud 7.0.4 (stable), I left a comment on the oc bug tracker, but as we are few em client users, there won’t be enough “pressure” - and all “mayor clients” (iphone contacts, android) seem to do a workaround - the chances are not good to get the “right” solution from oc. So maybe a workaround on em client would be the better solution for your customers, even if it is not your bug…

Hi, I’m sorry for the ongoing issues with Owncloud, I’ve submitted a workaround request to the developers, as the issue seems to be unresolved for quite a long time, hopefully the workaround could be included in one of the upcoming releases.

Thank you,
Paul