New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in vcard multiple REV/PRODID fields - This card is corrupted and has been fixed #129
Comments
I noticed there is a save button at the top in the contacts pages that have the exclamation point, next to the download and delete icons. However, when I click that I get the same error I documented above. When I try to download the card it fails. In my browser at the bottom it says: "Failed - Server problem" (This also fails when trying to download the contacts that have not been "fixed" and have no exclamation point in the interface.) I can click resume or cancel. These also fail. |
Okay, that what I thought :) |
No, I get an error when I try to download it. Is there another way to get at it? SQL query against postgres? cheers |
What is the error? Try opening the link to a new tab, I had this bug once! :) |
After rebooting just now I am able to download one of the cards. I changed some names and numbers, the rest should be as I downloaded it from the nextcloud contacts interface. Had to rename it to txt to upload also. |
Yep, this is coming directly from your vcard. There is too many REV fields, VERSION and PRODID. see required cardinality For your fix, just edit the raw vcard and remove the extra unwanted lines. |
Also, the error you get about the corrupted card comes from the vact that you use a comma into your groups. In your provided card, are you using two groups or one? |
Ok, thanks for looking into this. I have a couple of final questions however.
|
This may be an error after all I have the feeling. All flagged contacts do indeed have several groups assigned. I have no comma's in my groups, the comma is only exported (escaped as you see in the example I posted here) when downloading the contact. |
The comma is unescaped, so the group is displayed as 'xxx,zzz' instead of two groups: 'xxx' and 'zzz'. In the meantime, the error you get isn't coming from the warning about the groups. It is happening upon save when you edit/click the save button on this card because it has invalid fields cardinality (PRODID, REV) I can't tell you which to remove, but it shouldn't cause a lot of trouble if you keep the one you like the most. You can also remove the REV and PRODID. They will be replaced when you'll save the card later on. Keep only one VERSION and you'll be fine. |
The error can't come from having comma's in my groups, I don't have comma's in my groups. |
I assumed you had issues with your group based on the vcard you posted... 😕 Could you post a screenshot of the contact before you save please? |
Hi, If I stick to the example that snapet gave I adjusted as follows: (I had to attach an screenshot, otherwise the two backslashes that I removed were not displayed) to BEGIN:VCARD After a re-import it seems to work again for me. I believe it had to do with those backslashes. |
Don't remove the backslash on the tel parameter. 😲
It will fix the contact. Then if the contacts app displays a warning, you should be able to save the card again. |
Was just one contact anyway that had that backslash on the tel parameter. Had no impact at all. I re-added that contact, just in case. The other ones I cleaned up as you said
and now it works quite well, even the import of all contacts is now working as without any errors. |
Hi, Anyway, after searching quite long I ended up with the following update statement to clean up the double VERSION and PRODID entries and remove the REV line for one address book . I couldn't get my head around unescaping only the comma's in my CATEGORIES lines only, but that was only a save click, which you guys provide. |
I had a similar case that drove me crazy: I edited one certain contact and saved, no error. But upon reloading or syncing my smartphone contacts, I did not see my edits. Took me a while until I figured that the log contains a silent error which leads to the contact not being saved at all. In my case, it was a double REV:. Please make sure that ALL entries of the database are valid, and throw errors on the USER. Upon importing, upon saving, upon database migration, app update, etc. It's insane to have data INSIDE the database that the app cannot handle without noticing the user. |
I had the same problem with Nextcloud 13. Contacts could not be updated from the webinterface. But they could be updated from e.g., a phone using caldav. And after that those contact could be updated from the webinterface. I fixed it for all contacts by:
|
@elgaard Thanks for your SQL line.... you saved me so much time ! |
same issue here. Various owncloud / sabre multiple declaration:
A quick fix:
|
Steps to reproduce
Expected behaviour
I would expect the indicated fixed issue with the vcard to be permanently fixed and changed information to be saved.
Actual behaviour
I keep seeing the exclamation points and changed data is not saved.
Server configuration
Operating system:
Debian Testing 9.0
Web server:
Apache/2.4.25 (Debian)
Database:
postgresql-9.6 9.6.1-2 amd64
PHP version:
php7.0 7.0.15-1
php -v
PHP 7.0.15-1 (cli) (built: Jan 25 2017 10:17:41) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies
with Zend OPcache v7.0.15-1, Copyright (c) 1999-2017, by Zend Technologies
Nextcloud version: (see Nextcloud admin page)
Nextcloud 11.0.1 (stable)
Contacts version: (see Nextcloud apps page)
1.5.3
Updated from an older Nextcloud or fresh install:
Nextcloud updated several times, but problem started after latest Contact app update.
Signing status:
No errors have been found.
List of activated apps:
Enabled:
Disabled:
The content of config/config.php:
Are you using external storage, if yes which one: local/smb/sftp/...
no
Are you using encryption: yes/no
yes
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
no
Client configuration
Browser:
Firefox, Chromium
Operating system:
Opensuse Tumbleweed
CardDAV-clients:
Not relevant probably as I experience this problem from the browser interface.
Akonadi connector, CardDAV-Sync on Android 0.4.20, Outlook CalDav Synchronizer
Logs
Web server error log
/var/log/apache2/error_nextcloud.log is empty
Nextcloud log (data/nextcloud.log)
Below is just one entry, there are many.
Browser log
From Chromium console
The text was updated successfully, but these errors were encountered: