Summary | Calendar is not being loaded if the LDAP group that it was previously shared is no longer existing |
Queue | Horde Framework Packages |
Type | Bug |
State | Resolved |
Priority | 2. Medium |
Owners | jan (at) horde (dot) org |
Requester | ken.oncinian (at) gmail (dot) com |
Created | 02/24/2015 (3784 days ago) |
Due | |
Updated | 02/25/2015 (3783 days ago) |
Assigned | |
Resolved | 02/25/2015 (3783 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | Horde_Ldap 2.0.5 |
Patch | No |
State ⇒ Resolved
Milestone ⇒ Horde_Ldap 2.0.5
Queue ⇒ Horde Framework Packages
Priority ⇒ 2. Medium
commit c086f366bb9a44f3a1427bb124e43496b7d6a61a
Author: Jan Schneider <jan@horde.org>
Date: Wed Feb 25 16:45:42 2015 +0100
[jan] Don't throw exception from listUsers() if group not found
in LDAP directory (
Bug #13879).framework/Group/lib/Horde/Group/Ldap.php | 2 ++
framework/Group/package.xml | 4 ++--
2 files changed, 4 insertions(+), 2 deletions(-)
http://github.com/horde/horde/commit/c086f366bb9a44f3a1427bb124e43496b7d6a61a
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Calendar is not being loaded if the LDAP group that it was previously shared is no longer existing
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
entry <group ldap dn> no entry found" if the LDAP group that it was
previously shared is no longer available. While other applications
like Mnemo and Nag have no problem and will just have empty
permissions for sharing.