Maybe this works as designed, but...
I have created a custom ldap query with a filter. My filter is this:
(&(objectClass=user)(!(objectClass=computer))(!(objectClass=group))(!(cn=RC2*))(!(cn=Administrator))(!(cn=Admin)))
When I test the query, it comes back with the values I would expect.
Now, If I create a view against that query, it also works, until I add an exposed filter and set the filter. Then, the filter that is on my ldap query does not filter results.
Is that the way it is supposed to work? Is there any way for the exposed filters on the view 'inherit' the filters that are already on the LDAP Query?
thanks,
Cliff
Comments
Comment #2
grahlSounds like a bug, are you still experiencing this with current DEV or have you found a solution?
Comment #3
silverham CreditAttribution: silverham commentedLooks like possible duplicate: of #2847799 - LDAP Views filter is discarding LDAP query filter parameters.
Comment #4
grahlDuring the port to 8.x last week I saw this as well. It is definitely intentional in the 7.x code base. I've kept this behavior consistent for now but understand how that might be unwanted. I haven't yet found an indicator why this was done.
Comment #5
grahlClosing issue as outdated due to no further development on 7.x, if you feel this issue is still relevant and you are willing to work on a patch and/or debug the problem, please reopen.