| 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 | 09/18/2008 (6135 days ago) |
| Due | |
| Updated | 12/29/2008 (6033 days ago) |
| Assigned | 10/07/2008 (6116 days ago) |
| Resolved | 12/29/2008 (6033 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | Yes |
State ⇒ Not A Bug
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.
Assigned to Gunnar Wrobel
Assigned to Ben Klang
Priority ⇒ 1. Low
New Attachment: turba_save-without-rename.patch
Patch ⇒ Yes
Milestone ⇒
Summary ⇒ LDAP abook objects are always moved to _params['root'] DN
Type ⇒ Bug
State ⇒ Unconfirmed
Queue ⇒ Turba
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...