[#7356] "No such object" after ldap_rename
Summary "No such object" after ldap_rename
Queue Turba
Queue Version Git master
Type Bug
State Assigned
Priority 1. Low
Owners Horde Developers
Requester m.gabriel@das-netzwerkteam.de
Created 2008-09-18 (4780 days ago)
Updated 2010-09-24 (4044 days ago)
Assigned 2008-10-07 (4761 days ago)
Patch No

m.gabriel@das-netzwerkteam.de 2008-09-18 14:39:11
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 

sorry, no patch so far, but i will look at that later...

Gunnar Wrobel <wrobel@horde.org> 2008-12-29 08:48:20
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?

Jan Schneider <jan@horde.org> 2008-12-29 10:09:26
> @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.

Chuck Hagenbuch <chuck@horde.org> 2008-12-30 04:43:06
The save code should update the properties in the $contact object.

Gunnar Wrobel <wrobel@horde.org> 2008-12-30 10:14:00
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.