[#7354] LDAP abook objects are always moved to _params['root'] DN
Summary LDAP abook objects are always moved to _params['root'] DN
Queue Turba
Queue Version HEAD
Type Bug
State Not A Bug
Priority 1. Low
Owners bklang (at) horde (dot) org, wrobel (at) horde (dot) org
Requester m.gabriel (at) das-netzwerkteam (dot) de
Created 2008-09-18 (3836 days ago)
Updated 2008-12-29 (3734 days ago)
Assigned 2008-10-07 (3817 days ago)
Resolved 2008-12-29 (3734 days ago)
Patch Yes

2008-12-29 08:31:43 Gunnar Wrobel Comment #3
State ⇒ Not A Bug
Reply to this comment
Sorry for the delay.

Turba does not support hierarchical address books. The patch would 
only fix a configuration error.

If you use a LDAP sub structure on a writeable LDAP you will have to 
define several addressbooks in turba/config/sources.php. Each with its 
own root. You may not use

'scope' => 'sub'

for writeable address books. This makes only sense for read-only LDAP.
2008-12-22 03:31:35 Chuck Hagenbuch Comment #2 Reply to this comment
Gunnar, can you have a look at this? Thanks!
2008-10-07 13:53:44 Jan Schneider Assigned to Ben Klang
Assigned to Gunnar Wrobel
State ⇒ Assigned
2008-09-18 14:11:40 m (dot) gabriel (at) das-netzwerkteam (dot) de Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Summary ⇒ LDAP abook objects are always moved to _params['root'] DN
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ Yes
New Attachment: turba_save-without-rename.patch Download
Reply to this comment
when saving a turba LDAP object it is always moved to the base DN as 
specified in the source's _params['root'] DN. this behaviour 
gradiously destroy the fine ou/cn structure of an LDAP-subtree (scope 
= sub).

the attached patch tries to leave the turba LDAP object in place and 
only if that fails it moves the object  to the _params['root'] DN...

hope someone likes it...

@kolab-people: this fix allows it to edit contats in cn=external via 
horde without destroying the kolab LDAP tree...

Saved Queries