Closed thomasrussellmurphy closed 10 years ago
I'm currently experiencing this very same issue. I've looked through the code and can't spot any obvious reasons to why it isn't working. Any ideas?
yes, I seem to be able to reproduce. The code that's supposed to respect this doesn't seem to have changed in a while, but I guess it's stopped working in more recent versions of BL. I'll try and figure it out.
Blacklight accidentally broke backwards compat of a SolrHelper#find
method way back in BL 4.0, breaking blacklight_advanced_search, and introducing a really awkward api for SolrHelper#find
.
The new api is, IMO buggy, but it's also been there since 4.0. I'm not sure if I should write to the weird buggy api, or do something else.
I believe this has been fixed by #10.
Trying to limit what facet fields are included on the search form may still interact weirdly with pivot facetting and the tag/exclude facet features supported by newer BL's, if you're using them. I don't understand enough about how those work to know what's going on and how to deal with it, but I think it's a different issue -- the form_solr_parameters
should now be correctly merged into Solr request params when making the solr request to get facet values for the advanced search form page.
There will shortly be a new BL 4.x-compatible release incorporating this and other fixes and improvements.
Sorry it took so long for someone to get to this!
Inside my
configure_blacklight do |config|
block, I have added:However, the
/advanced
view is displaying the default facets from the Solr search requestHandler. Furthermore, the log output from Solr that corresponds to loading the advanced search is:This indicates that nothing is being changed by setting
:form_solr_parameters
inconfig.advanced_search
. Am I missing something or is this really not working? Adding a:qt
that doesn't exist to theconfig.advanced_search
does produce an error, so the variable is being set.