-
Notifications
You must be signed in to change notification settings - Fork 178
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
Show more details about the failing reason of an import #990
Comments
Yes, this is a plan feature :) The main issue is how to manage the display when you have 100 contacts that failed on import, we don't want to flood the Interface with data 🤔 How would you like having this info? 🤔 |
Good to know :) Actually I wanted to import over hundreds of vcards, to import the contacts from my phone. As a quick bugfix I would recommend adding an ok button to the importing dialog, so it doesn't close automatically. So you can at least see that there is something wrong with the file you wanted to import and not expect the import function to be broken at the moment. The info would be nice to have just under the importing dialog after it is finished. You don't need to display all the errors, just make an expandable box which is just one line and you can expand it to view the details of the errors. Does this make sense? |
Awesome! This is also planned here: #606 🎉
Totally does! Let's make this issue about this! :) |
I just did an import of contacts, and it’s not that many, around ~200. But ~50 of them failed. Now that I closed the import window there’s no way I can know which ones of them failed, and they are not displayed. I’d say that "failed" import, for whatever reason, should not lead to the contacts not displaying at all. Some of it has to be salvageable, like the name or some fields, no? It would be way better to show entries for all the contacts so you at least have some indication, but with an "Error" icon of some sort so you can fix it. |
depends on the errors. We fix the one we can, otherwise it's either, not implemented by the library, or not fixeable by us :) Do you have more input on the errors Jan? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Found this Issue while having trouble to import Contacts exported from my Android into Nextcloud. Problem: Nextcloud seems to only support vcf 3.0, Android exports vcf 2.1. Solution: Using this project I was able to convert all my contacts to 3.0. After that the import ran through with 0 errors on 385 contacts. |
This comment has been minimized.
This comment has been minimized.
Please don't, we do not support vcard 2.1, and there is already an opened issue #492 ;) |
From a user perspective, it would be pretty cool, if all the importers of NC could adapt to a similar (more descriptive) UI pattern: |
Maybe we can add a solution to the warning: If someone tries to import a 2.1 vcard, there could be a warning like this: "You tried to import a vCard in the old v2.1 format. please convert it to v3.0. e.g. with this conversion script: https://github.com/jowave/vcard2to3 or online with https://labs.brotherli.ch/vcfconvert/" |
I had a similar issue, where it reported "2 errors" - I had to look into the logs as admin to find out that it was a wrongly formatted field and thus two birthdays would have gone missing :/ |
I got this #492 and only with a search online I found those tickets. |
Recently an import failed because TYPE= was missing for TEL, and there was nothing at all in the logs. |
Is there any way to tell what exactly went wrong? There appears to be no log whatsoever on the server either. I just need to get some sort of identifier on the one contact out of 200 that failed to import. Also to anyone seeing a large amount of failures: Ensure you're not using sqlite as nextcloud does not appear to implement concurrency properly with it and it fails to import a large random chunk of your contacts due to race conditions. |
When importing a vcf file exported by the google calendar app on android the contacts app opens the import windows, and closes it again immediately afterwards. Nothing was imported, no error messages given.
I guess the exported vcf file is in an invalid format, but even if I change it to a (I guess) valid format it fails silently on version 2.1. I would expect a message that this vcf version is not supported or that there is something wrong with the vcf format. In the best case also help for what to do.
To Reproduce
Import the vcard (invalid format):
or the vcard (with valid format):
When changing the version in the last vcard to 3.0 it imports properly.
Expected behavior
The contacts app should display an error message that the vcard couldn't be imported and state the reason for that (Invalid format or old vcard version).
Actual behavior
The importing dialog opens and closes immediately afterwards, nothing can be seen there.
Server configuration
Operating system: Linux
Web server: Apache
Database: MariaDB
PHP version: 7.2
Nextcloud version: 15.0.5
Contacts version: 3.0.5
Updated from an older Nextcloud or fresh install:
Updated from an older nc instance
Signing status:
List of activated apps:
Nextcloud configuration:
Client configuration
Browser:
Googel Chrome 72.0.3626.121
Operating system:
Windows 10
CardDAV-clients:
DAVDroid
Logs
Web server error log
nothing related
Nextcloud log
data/nextcloud.log
Browser log
For the vcard with a valid format and a wrong version
For the vcard with a invalid format and a wrong version
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: