-
Notifications
You must be signed in to change notification settings - Fork 166
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
ADR "mismatch" between vcard and GUI, formatted (LABEL) vs detailed address, leading to sync confusion #1900
Comments
I want to confirm this issue. the LABEL field is not updated correctly (read: at all) if the address field is edited. They should be kept in sync. |
@brjhaverkamp why do you think the address and label should sync? As per the RFC example,
the label is not synched with the address. The LABEL is free text and optional.
|
This problem occurs from time to time; also with another server's Web UI for contacts. I wonder whether it would be the best solution on DAVx5 side that it should parse incoming
What do you think about that? Or do you have other suggestions how DAVx5 could improve compatibility with Nextcloud (and other servers) in that matter? |
I don't think that is the best solution. But I would like to have an option that Nextcloud Contacts is intelligent enough to update the LABEL tag from the address field. |
This issue seems to be a duplicate of #1667. |
Further versions of DAVx⁵ won't send the If anyone is interested in testing, please let me know. |
That looks like a good solution to not break the formatted label in Nextcloud. |
Steps to reproduce
Prereq: Existing "simple" contact, e.g. just FN set, already synched between Nextcloud and via DAVx5 to an Android device.
FYI in my case FOSS (F-Droid) App Simple-Contacts, v 6.13.0, Android 10, Nokia 7.2
FYI Simple-Contacts per design does not use detailed addresses, just one multiline address field, finally stored as ADR->STREET
Remark: When contact is now downloaded from Nextcloud, NC creates NON-compliant V3.0 vcard with an ADR like
LABEL param inside ADR was introduced by RFC 6350, valid for vcard 4.0, ch. 6.3.1..
This LABEL param deprecates old v3.0 LABEL type defined in RFC 2426 ch. 3.2.2. Which had to be defined as separate vcard node, if vcard version is/should be 3.0 as used by Nextloud GUI export function.
FYI I've opened #1899 yesterday, got the impression that Nextcloud more or less is exporting V4.0 vcards although declarating them as V3.0
Downloaded from Nextcloud (V3.0 incompliant as described above) vcard looks as follows:
IHMO keeping the previous LABEL value without showing it in GUI is more than confusing, and hard to detect(*)!
Shown in GUI:
That's what I mean with (*) hard to detect: As vice versa on Android only the formatted LABEL address is shown, I thought at first that this might be a DAVx5 bug.
FYI When synched to iOS, with native cardDAV support, detailed address seems to be used by default, in contrast to Android.
Expected behaviour
If desired by design both detailed address and formatted address, as defined by RFC, should be available in Nextcloudm both have to be shown/changeable in GUI.
If LABEL is used/created en passant, so hidden by design, it should be in sync/regenerated based on detailed address, to avoid the described above confusion.
Actual behaviour
Nextcloud keeps "hidden" formatted address, unchanged
Server configuration detail
Operating system: Linux 5.3.18-lp152.47-default #1 SMP Thu Oct 15 16:05:25 UTC 2020 (41f7396) x86_64
OpenSuse Leap 15.2
Webserver: Apache (apache2handler)
Database: mysql 10.4.14
PHP version:
7.4.6
Modules loaded: Core, date, libxml, pcre, filter, hash, Reflection, SPL, session, SimpleXML, standard, xml, mysqlnd, apache2handler, apcu, bcmath, bz2, ctype, curl, dom, mbstring, fileinfo, ftp, gd, gettext, gmp, iconv, imagick, intl, json, ldap, exif, mysqli, openssl, pcntl, PDO, pdo_mysql, pdo_sqlite, zlib, posix, soap, sockets, sqlite3, tokenizer, xmlreader, xmlwriter, zip, Phar, Zend OPcache
Nextcloud version: 20.0.1 - 20.0.1.1
Updated from an older Nextcloud/ownCloud or fresh install:
Upgraded from Owncloud long ago
Where did you install Nextcloud from:
RPM based from OpenSuse repos
Signing status
Array
(
)
List of activated apps
Configuration (config/config.php)
Are you using external storage, if yes which one: local/smb/sftp/...
Are you using encryption: 1
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
Client configuration
Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.111 Safari/537.36
Operating system:
Logs
Web server error log
Nextcloud log
Browser log
The text was updated successfully, but these errors were encountered: