Bug 234259

Summary: remove 'Traditional Addressbook' resource option
Product: [Applications] kaddressbook Reporter: kavol <kavol>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: krammer, tokoe
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description kavol 2010-04-13 16:00:23 UTC 
Version:            (using KDE 4.4.2)
OS:                Linux
Installed from:    Fedora RPMs

Run kaddressbook, add addressbook

There is an option "KDE Address Book (traditional)". This should NOT be present - I refer to bug #234080 comment #1:

"'Traditional Addressbook' or 'vCard file' resource? The former shouldn't be used anymore."

If you choose this, here's how to reproduce a problem:

A wizard is run ...
Step 1 - select file
Step 2 - select vCard, enter path (~/.kde/share/apps/kabc/std.vcf)
Step 3 - do not check read only

Add a contact into that addressbook. Quit kaddressbook. The std.vcf file is left untouched, the newly added contact does not get saved to it.
Comment 1 Kevin Krammer 2010-04-17 11:51:39 UTC 
The compatibility resource is actually just a temporary mechanism that will be removed once all backends are supported natively, i.e. by respective specialized Akonadi resources.

Maybe it would make sense to have some kind of blacklisting where plugins that provide functionality which is already available natively are no longer shown in the plugin selection dialog, thus avoiding them being used instead of the respective native resource.
Comment 2 Anders Lund 2012-02-01 14:50:26 UTC 
The "Traditional addressbook" is still offered in KDE 4.8. Is it needed?
Comment 3 Denis Kurz 2016-09-24 20:52:05 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 4 Denis Kurz 2017-01-07 22:50:06 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.