Active
Project:
Apache Solr Search
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 May 2014 at 17:26 UTC
Updated:
24 Jun 2015 at 19:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
nick_vhThis is an Apache Solr Term problem. Moving it
Comment #2
robbertnl commentedWhats the status? Same issue here.
Comment #3
jamesrward commentedWe are experiencing the same issue. @Nick_vh any ideas where the issue lies in Apachesolr Term so we can try to resolve this ourselves?
Comment #4
jamesrward commentedComment #5
jamesrward commentedI'm inclined to go back to blaming this on apachesolr_access since a change to this code will fix the issue:
The fact that
$node_access_query->addFilter('hash', apachesolr_site_hash());is only called for users with bypass node access set appears to be the cause of this issue and the related issue for ApacheSolr User. This patch fixes both issues but is not the most elegant solution.To me it appears that the ApacheSolr Access module shouldn't be preventing the site hash from being added to the filter for users without bypass node access. I see no documentation of using this as a method to restrict search access to specific users. I would very much like to see this issue moved back to ApacheSolr Access
Comment #6
jamesrward commentedThis patch addresses the issue for me and I think makes the access submodule more logical. I'd want to see some tests from those running sites with more restrictive node access rules.
Comment #7
jamesrward commented