Tickets :: [#7356] "No such object" after ldap_rename

6.0.0-alpha10

5/14/25

Summary	"No such object" after ldap_rename
Queue	Turba
Queue Version	Git master
Type	Bug
State	Assigned
Priority	1. Low
Owners	Horde Developers (at)
Requester	m.gabriel (at) das-netzwerkteam (dot) de
Created	09/18/2008 (6082 days ago)
Due
Updated	09/24/2010 (5346 days ago)
Assigned	10/07/2008 (6063 days ago)
Resolved
Milestone
Patch	No

09/24/2010 10:26:21 PM	Jan Schneider	Version ⇒ Git master

12/30/2008 10:14:00 AM	Gunnar Wrobel	Comment #5	Reply to this comment
As far as I know the save code updates the contact properties. It is just the edit page that prefers the old url over the contact properties.

12/30/2008 04:43:17 AM	Chuck Hagenbuch	Summary ⇒ "No such object" after ldap_rename

12/30/2008 04:43:06 AM	Chuck Hagenbuch	Comment #4 Taken from Ben Klang Taken from Gunnar Wrobel Taken from Chuck Hagenbuch Taken from Jan Schneider Assigned to Horde Developers	Reply to this comment
The save code should update the properties in the $contact object.

12/29/2008 10:09:26 AM	Jan Schneider	Comment #3	Reply to this comment
@Chuck, Jan: Is that the intended way of operation? No, because you can also edit contacts from the browse views, and you don't want to "return" to the contact view in those cases.

12/29/2008 08:48:20 AM	Gunnar Wrobel	Comment #2 Assigned to Jan Schneider Assigned to Chuck Hagenbuch	Reply to this comment
Yes, line 86 to 87 in turba/edit.php says: $url = Util::getFormData('url'); header('Location: ' . (empty($url) ? $contact->url('Contact', true) : $url)); And $url will be set to the old contact id. If we can safely assume that we always want to return to the contact view after editing we could modify the above snippet to header('Location: ' . $contact->url('Contact', true)); @Chuck, Jan: Is that the intended way of operation?

10/07/2008 01:54:16 PM	Jan Schneider	Assigned to Ben Klang Assigned to Gunnar Wrobel State ⇒ Assigned

09/18/2008 02:39:11 PM	m (dot) gabriel (at) das-netzwerkteam (dot) de	Comment #1 State ⇒ Unconfirmed Patch ⇒ No Milestone ⇒ Queue ⇒ Turba Summary ⇒ LDAP abook: "No such object" after ldap_rename Type ⇒ Bug Priority ⇒ 1. Low	Reply to this comment
in case an LDAP object has to be renamed (cn attribute is edited and changed in turba's contact.php, cn makes up the object's RDN), it will not be reloaded after saving. instead of the modified object the address book list is loaded. somehow the new $object_id is not passed back to the reloaded contact.php... sorry, no patch so far, but i will look at that later...