Working Part: When I try to add custom fields for a contact (only selected contact) they work properly. I can select fields' data types (text, number, link etc.) without any problem and it works. Broken Part: 1-) But when I create a custom field (url data type) will be used for "all" contacts "url field" turns to "text field". 2-) If there are more than one custom field you cannot delete "selected" custom field but other. Usecase: I try to add contacts' additional websites by custom fields because KAddress Book supports only "one" website and a blog url addresses. Today everyone/company has many websites as Facebook, Twitter, Instagram, Linkedin etc. Only the way I try to add those web addresses custom fields. Reproducible: Always Steps to Reproduce: A-) Create Custom Fields 1. Open a contact card. 2. Add custom field for use of all contacts. 3. Change its data type to url and save. 4. Try to enter a web address to the custom field and save. 5. Open the contact (view mode) and there is no any url. 6. Go to edit custom field and see field's data type turned to "text". B-) Delete Custom Fields 1. Open a contact card. 2. Select one of the custom fields (they should be more than one) 3. Try to delete selected contact. 4. It deletes other one not selected. Expected Results: I indicated above. I indicated above.
I have mistakenly typed incorrect word above as described below.. B-) Delete Custom Fields 1.... 2... 3. Try to delete selected custom field (not contact) 4...
I have the same (similar?) problem, I think. I'm running KAddressbook v5.1.3 on Kubuntu 16.04. My use case has been to try and make a global custom date field. However, I am constantly running into lots of little bugs surrounding custom fields. Reproducible: Always Steps to reproduce: 1. Create a new user, give it a name and create a new Custom Field, setting the Type to Date and not checking the 'use for all contacts'. This seems to work, and I input a date and close the contact view. 2. Edit the contact and add one more date field. Still seems to work fine. 3. Make a new contact and give it a name. Everything is still fine with the first user. 4. Edit the first contact and make a Custom Field of type Date and check 'use for all contacts', put in a date and save the contact. In the view pane something looks strange with the new date field (it is formated differently than the first two). Go back to the contact and the Custom Fields tab. Select the third custom field and click Edit. In the Edit Custom Field box, the Title has now been set to the Title of the first custom field, and the Type to Text. 5. Make a new contact, give it a name and save it. When checking the first contact now, both the first and third custom fields have their Title's set to the Custom Fields' ID, and their Types have been set to Text. The 'use for all contacts' field has also been unchecked for both. 6. Furthermore, and Custom Field for all contacts has its Type set to Text when trying to edit it from another contact. Finally, I've tried to export my contacts and putting them all in one file. When looking at the vcf-file, I can see the Custom Fields, but all the values are formated as if they are Text fields, and there is no information about the Type of the fields.
I looked through the bug list, and I think all the following unconfirmed bugs are related to the same problem(s): https://bugs.kde.org/show_bug.cgi?id=340316 https://bugs.kde.org/show_bug.cgi?id=339959 https://bugs.kde.org/show_bug.cgi?id=299704 https://bugs.kde.org/show_bug.cgi?id=299853 https://bugs.kde.org/show_bug.cgi?id=300087 Additionally, this feature request could probably be implemented easily while fixing this: https://bugs.kde.org/show_bug.cgi?id=317774
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!