The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.as of http://drupal.org/node/1375104#comment-5569528
current search block links aren't covered, as the current_search isn't aware of the url_processor, yet
we still need to figure out, how to integrate with facetapi in order to implement this functionality the most efficient way.
Comments
Comment #1
cpliakas commentedInteresting. Without looking at the code I would think it would have access to the URL processor through the adapter, but let me take a closer look.
Comment #2
dasjoideally, i would like to reuse / adapt the postProcessItem function to work both for the general facet handling + the current_search specific one.
but so far, i have seen that the configuration / render arrays being passed differ, so it is hard for me to code a generic solution.
generally speaking, the getQueryString function are quite pluggable. we could also think about doing something similar for the paths being set. but i guess this would require some hacking / rewriting and i'm not sure i can do this alone..
Comment #3
cpliakas commentedYes, ideally there should also be a getFacetPath() API method or something. I'll take a quick look at the code to see if there is something we can do.
Comment #4
dasjohi chris,
do you have news on this?
i would like to get this further until the end of the week. also of interest might be #1434462: ApacheSolr module integration
Comment #5
dasjocurrent search block integration has been committed.
requires #1441302: Current search integration for FacetapiUrlProcessor postProcessing to alter paths
Comment #6
cpliakas commentedThis looks good with the current functionality. After thinking about this, I am proposing a different approach at http://drupal.org/node/1375104#comment-5612412.
Comment #7
dasjo