Tickets :: [#6362] Group LDAP backend returns error for "Empty result"

6.0.0-alpha12

6/10/25

Summary	Group LDAP backend returns error for "Empty result"
Queue	Horde Framework Packages
Queue Version	HEAD
Type	Enhancement
State	Resolved
Priority	1. Low
Owners	chuck (at) horde (dot) org
Requester	asmarre (at) ull (dot) es
Created	03/03/2008 (6308 days ago)
Due
Updated	11/16/2008 (6050 days ago)
Assigned
Resolved	11/16/2008 (6050 days ago)
Milestone
Patch	No

11/16/2008 10:24:42 PM	Chuck Hagenbuch	State ⇒ Resolved

11/05/2008 07:46:06 PM	Chuck Hagenbuch	Comment #4 State ⇒ Feedback	Reply to this comment
The original ticket was about getGroupMemberships, and that function is patched. Where are you seeing an issue?

11/05/2008 01:37:46 PM	kris (at) kayell (dot) com	Comment #3	Reply to this comment
This isn't showing up in version 3.3. I had to apply the patch to this version to get rid of that message. [Show Quoted Text - 10 lines][Hide Quoted Text] The function getGroupMemberships of the Horde/Group/ldap.php returns an error where the result of a query is empty. I'm not sure if this behaviour is correct, I manage a LDAP where the majority of the users don't are members of a group (but have a primaryGroup attribute in their user entry). I suggest to return array(); instead of the error. I attach a patch for the version 1.18.2.2 of the file (I hope it will be ok for newer versions).

03/04/2008 08:58:02 PM	Chuck Hagenbuch	Comment #2 State ⇒ Resolved Assigned to Chuck Hagenbuch	Reply to this comment
Makes sense - committed, thanks.

03/03/2008 01:53:13 PM	asmarre (at) ull (dot) es	Comment #1 Priority ⇒ 1. Low Type ⇒ Enhancement Summary ⇒ Group LDAP backend returns error for "Empty result" Queue ⇒ Horde Framework Packages New Attachment: group_ldap_empty_result_ok.diff State ⇒ New	Reply to this comment
The function getGroupMemberships of the Horde/Group/ldap.php returns an error where the result of a query is empty. I'm not sure if this behaviour is correct, I manage a LDAP where the majority of the users don't are members of a group (but have a primaryGroup attribute in their user entry). I suggest to return array(); instead of the error. I attach a patch for the version 1.18.2.2 of the file (I hope it will be ok for newer versions).