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 (4555 days ago) |
Due | |
Updated | 2010-09-24 (3819 days ago) |
Assigned | 2008-10-07 (4536 days ago) |
Resolved | |
Milestone | |
Patch | No |
just the edit page that prefers the old url over the contact properties.
Assigned to
Taken from Jan Schneider
Taken from Chuck Hagenbuch
Taken from Gunnar Wrobel
Taken from Ben Klang
don't want to "return" to the contact view in those cases.
Assigned to Chuck Hagenbuch
Assigned to Jan Schneider
$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?
Assigned to Gunnar Wrobel
State ⇒ Assigned
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Summary ⇒ LDAP abook: "No such object" after ldap_rename
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ No
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...