Bug 339959

Summary:	custom fields of contacts get mixed
Product:	[Applications] kaddressbook	Reporter:	Carioca <h6zb8-kdebugs20120801>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	montel, tokoe
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Carioca 2014-10-14 13:38:40 UTC

The custom fields of contacts get mixed, e. g. I have two custom fields and click the edit-button, the edit-dialog has in the title-field the title of the other, not selected field. Also I created them as boolean, then they became text-fields.

Reproducible: Always

Steps to Reproduce:
1. create more then one custom fields with type boolean or numeric or else except text.
2. close the edit-dialog of this contact.
3. open the edit-dialog of this contact and edit the custom fields with the edit-button.

Actual Results:  
Everything is mixed and wrong

Expected Results:  
keep the correct titles and types.

Comment 1 Laurent Montel 2014-10-14 18:03:32 UTC

Interesting bug. 
I will investigate soon.

Comment 2 Laurent Montel 2014-10-14 18:07:10 UTC

it works fine here.
Could you give me more infos ?
Which type of calendar ? imap calendar ? local calendar ?

kdepim version ?

Comment 3 Carioca 2014-10-14 21:53:35 UTC

It is a local calender. Version is 4.13.3.

It does not work correctly here. I am surprised it works fine at you.

Comment 4 Laurent Montel 2014-10-15 05:59:09 UTC

I retested it and work fine.
So I don't know

Comment 5 Carioca 2014-10-15 10:57:55 UTC

I tried at another PC with KDE and get the same. But I figured out that the problem only occures when you sort the titles like 3,2,1. The intern sort stays 1,2,3. Someone did a very bad programming there. Even deleting leads to strange new fields.

Can you try again, please?

Comment 6 Carioca 2014-10-15 11:07:04 UTC

The custom boolean fields change to text field when you enable ‘Use field for all contacts’.

Comment 7 Denis Kurz 2016-09-24 20:53:00 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kaddressbook (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 8 Denis Kurz 2017-01-07 22:03:33 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.