Bug 286592 - LDAP server not updated with local modifications
Summary: LDAP server not updated with local modifications
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-14 13:27 UTC by Aurélien
Modified: 2017-01-07 22:43 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aurélien 2011-11-14 13:27:19 UTC
Version:           unspecified (using KDE 4.7.3) 
OS:                Linux

When a LDAP entry is updated (with kaddressbook) modifications are not propagated to the LDAP server. Moreover if a new contact is added to a LDAP resource (with kaddressbook) the contact is not added to the LDAP server.

Reproducible: Always

Steps to Reproduce:
1. Update a contact contained in a LDAP resource with kaddressbook
2. Check the consistency of your LDAP server with another tool and compare the contact entry
3. Mismatch..

or
1. Add a contact to a LDAP resource
2. Try to find the new contact on your LDAP server with another tool
3. The new contact doesn't exist

Actual Results:  
The contact entry is not updated or the new contact is not present

Expected Results:  
The contact entry have to be updated and the new contact added to the LDAP server.

I always seen this bug.. It never worked since kaddressbook uses akonadi!
Comment 1 Steven Coutts 2013-08-10 15:27:34 UTC
Looks like an old but I am still seeing this, anyone any ideas if this is likely to get fixed ever?
Comment 2 tony den haan 2014-06-25 14:02:08 UTC
same here, failing silently
Comment 3 Steven Coutts 2014-11-19 16:19:35 UTC
And here we are over a year later, still same bug
Comment 4 Rolf Eike Beer 2015-03-04 21:51:26 UTC
Maybe this is related to bug 334985?
Comment 5 Denis Kurz 2016-09-24 20:52:38 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 6 Denis Kurz 2017-01-07 22:43:18 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.