You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Import vcard file with several valid and invalid vcards (caused by bugs in the application(s) generating this file)
The import for the invalid cards fails, showing only a few-word popup message that the import of some card failed.
Expected behaviour
The error message should provide understandable information about which card(s) failed to
import, and optimally, why. This information should be accessible to the user who initiated the import of the faulty file
Actual behaviour
The error message basically only says "didn't work" a few times, but it does not indicate at all for which vcards the import failed, nor does it give any summary information after the import which tells how many failures we got.
Also the NextCloud error log (which probably is not accessible for the normal user?) visble from the web interface contains an entry for each failed card, but it's still not possibly to derive the actual cards which failed based on the information in the log as the vcard data there is abbreviated in a way which makes them unidentifiable.
(The log file stored on the server contains the necessary information, but really is not accessible to any user except the NextCoud sys admin.)
I understand that it's probably not easy to provide information about which cards failed as just those cards could not be processed and the information within possibly cannot be extracted because of this.
Still, the current behaviour is very unsatisfying. I'm an experienced software developer and (less experienced) sysadmin and could trace the problem down to illegal vcard property names contained in the affected cards, but any less experienced user would be stuck, I fear.
Server configuration
Operating system: Debian GNU/Linux Stretch
Web server: Apache 2.4
Database: MariaDB 10.1
PHP version: 7.0
Nextcloud version: 14.0.1
Updated from an older Nextcloud/ownCloud or fresh install: fresh install
GitMate.io thinks possibly related issues are #6776 (Import of Outlook VCARD failing), #4105 (Mentioning inexistent user has strange feedback), #8409 (NC13 Users Personal Information Does Not Save), #2143 (Visualize useful synthetic information when user clicks 'Tags' ), and #424 (User import/export migration ability).
Steps to reproduce
Expected behaviour
The error message should provide understandable information about which card(s) failed to
import, and optimally, why. This information should be accessible to the user who initiated the import of the faulty file
Actual behaviour
The error message basically only says "didn't work" a few times, but it does not indicate at all for which vcards the import failed, nor does it give any summary information after the import which tells how many failures we got.
Also the NextCloud error log (which probably is not accessible for the normal user?) visble from the web interface contains an entry for each failed card, but it's still not possibly to derive the actual cards which failed based on the information in the log as the vcard data there is abbreviated in a way which makes them unidentifiable.
(The log file stored on the server contains the necessary information, but really is not accessible to any user except the NextCoud sys admin.)
I understand that it's probably not easy to provide information about which cards failed as just those cards could not be processed and the information within possibly cannot be extracted because of this.
Still, the current behaviour is very unsatisfying. I'm an experienced software developer and (less experienced) sysadmin and could trace the problem down to illegal vcard property names contained in the affected cards, but any less experienced user would be stuck, I fear.
Server configuration
Operating system: Debian GNU/Linux Stretch
Web server: Apache 2.4
Database: MariaDB 10.1
PHP version: 7.0
Nextcloud version: 14.0.1
Updated from an older Nextcloud/ownCloud or fresh install: fresh install
Where did you install Nextcloud from: tar.gz
Signing status:
No errors have been found.
List of activated apps:
Enabled:
Disabled:
Nextcloud configuration:
{
"system": {
"instanceid": "REMOVED SENSITIVE VALUE",
"passwordsalt": "REMOVED SENSITIVE VALUE",
"secret": "REMOVED SENSITIVE VALUE",
"trusted_domains": [
"nextcloud.ohrner.net"
],
"datadirectory": "REMOVED SENSITIVE VALUE",
"dbtype": "mysql",
"version": "14.0.1.1",
"overwrite.cli.url": "https://nextcloud.ohrner.net",
"dbname": "REMOVED SENSITIVE VALUE",
"dbhost": "REMOVED SENSITIVE VALUE",
"dbport": "",
"dbtableprefix": "oc_",
"mysql.utf8mb4": true,
"dbuser": "REMOVED SENSITIVE VALUE",
"dbpassword": "REMOVED SENSITIVE VALUE",
"installed": true,
"memcache.local": "\OC\Memcache\APCu",
"memcache.locking": "\OC\Memcache\Redis",
"redis": {
"host": "REMOVED SENSITIVE VALUE",
"port": 6379
},
"mail_smtpmode": "smtp",
"mail_smtpauthtype": "PLAIN",
"mail_from_address": "REMOVED SENSITIVE VALUE",
"mail_domain": "REMOVED SENSITIVE VALUE",
"mail_smtphost": "REMOVED SENSITIVE VALUE",
"mail_smtpport": "25",
"mail_smtpsecure": "tls",
"updater.secret": "REMOVED SENSITIVE VALUE",
"maintenance": false,
"theme": "",
"loglevel": 2
}
}
Are you using external storage, if yes which one: local
Are you using encryption: no
Are you using an external user-backend, if yes which one: currently only local users
Client configuration
Irrelevant
Logs
Web server error log
Not relevant
Nextcloud log (data/nextcloud.log)
Contains the relevant information, see above.
Browser log
Not relevant
The text was updated successfully, but these errors were encountered: