6.0.0-git
2018-12-15

[#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 (at)
Requester m.gabriel (at) das-netzwerkteam (dot) de
Created 2008-09-18 (3740 days ago)
Due
Updated 2010-09-24 (3004 days ago)
Assigned 2008-10-07 (3721 days ago)
Resolved
Milestone
Patch No

History
2010-09-24 22:26:21 Jan Schneider Version ⇒ Git master
 
2008-12-30 10:14:00 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.
2008-12-30 04:43:17 Chuck Hagenbuch Summary ⇒ "No such object" after ldap_rename
 
2008-12-30 04:43:06 Chuck Hagenbuch Comment #4
Assigned to Horde DevelopersHorde Developers
Taken from Jan Schneider
Taken from Chuck Hagenbuch
Taken from Gunnar Wrobel
Taken from Ben Klang
Reply to this comment
The save code should update the properties in the $contact object.
2008-12-29 10:09:26 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.
2008-12-29 08:48:20 Gunnar Wrobel Comment #2
Assigned to Chuck Hagenbuch
Assigned to Jan Schneider
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?
2008-10-07 13:54:16 Jan Schneider Assigned to Ben Klang
Assigned to Gunnar Wrobel
State ⇒ Assigned
 
2008-09-18 14:39:11 m (dot) gabriel (at) das-netzwerkteam (dot) de Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Summary ⇒ LDAP abook: "No such object" after ldap_rename
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ No
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...

Saved Queries