I am trying to integrate lucene api search to my site. But have run into an issue with my ad servers. The URL is example.com/search/luceneapi_node/{querystring} . The problem is that "luceneapi_node" in the url generates ads that are related to lucene and open source. This is a business journal magazine site with ads coming from various feeds and networks. So getting rid of or changing the url path is ideal here.

How do I change the url path or create an apache redirects to go to an ideal "/search/site/{querystring}" or "/search/qry/{querystring}"

Comments

cpliakas’s picture

cpliakas commented
Status: Active » Postponed

Hi dlo001.

I have done some research to find a workaround, but I haven't come up with one. The problem is that Search Lucene API relies on the core Search API, which pulls the search keys from the path. Furthermore, Search Lucene API makes use of the search_get_keys() function which is the root of the problem along with the hard coded menu definitions. The only other solution I can think of is to expand the Search Lucene Views module so that the location of the search keys in the path can be altered. We would have to find some way to make the facets available to the view, which is currently not supported. This is a good support request, but it would require some rethinking to get this implemented, which I am definitely not opposed to.

Sorry,
Chris

cpliakas’s picture

cpliakas commented
Status: Postponed » Closed (won't fix)

It seems like using Search Lucene Views won't be a viable option until Views 3 is available. Since this is more of a core Search issue, I am respectfully marking this as "won't fix", although I think it is very necessary functionality. Hopefully the core Search module will provide the ability to decouple the search query from the path in the future.