Description
Describe the bug
group properties as defined in vacrd RFCs v3 used to be viewable and editable in the old UI.
Now they are neither visible nor editable.
Steps to reproduce
import a vcf similar to
BEGIN:VCARD
VERSION:3.0
UID:rakefet-0c992
ADR;TYPE=HOME:;;Avenue de l'AAA;Bruxelles;;1180;Belgium
BDAY;VALUE=DATE:19540321
EMAIL;TYPE=HOME:[email protected]
FN:Cécile Maaaak
GENDER:F
N:Maaaak;Cécile;;;
RAK1.NICKNAME:Asher
RAK2.NOTE:archivé sept 2014
RAKR.RELATED;TYPE=SPOUSE;VALUE=TEXT:Julian Serais
REV;VALUE=DATE-AND-OR-TIME:20230311T095516Z
TEL;TYPE=CELL:+32 48 010101001
RAK1.X-ABLABEL:Hebrew
RAK2.X-ABLABEL:Rak-Note Fam
END:VCARD
Expected behavior
the properties grouped as RAKxx. (RAK1, RAK2 RAKR for nickname note and related) used to be displayed and usable as supplemental fields.
it is true that such group fields are application specific and could be ignored, according to the RFC. Theses specific group properties and contact are created by an external app, but it is critical for us to be able to see these fields in nextcloud and this used to work well in the previous contact app.
Perhaps a list or regex of group could be explicitely specified in order to be allowed in nextcloud contact app. This would allow to respect the new default behaviour and avoid messing with custom data.
Actual behavior
the said fields are invisible in the UI
Contact version
5.3.0
Operating system
Mint 21.1
PHP engine version
PHP 8.1.2
Web server
Nginx
Database
MariaDB
Additional info
No response