Hi
On a dev project, the module overwrites the default search engine. In this case it is solr.
It provides the core search as standard.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | solr_search2.patch | 356 bytes | jdanthinne |
| #3 | custom_solr.patch | 350 bytes | jdanthinne |
Hi
On a dev project, the module overwrites the default search engine. In this case it is solr.
It provides the core search as standard.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | solr_search2.patch | 356 bytes | jdanthinne |
| #3 | custom_solr.patch | 350 bytes | jdanthinne |
Comments
Comment #1
jdanthinne commentedHi,
unfortunately, I don't have a server with solr installed to test that... so it's difficult to find where the problem is.
Can you tell me exactly:
Comment #2
bennos commentedit is a global test server, just for testing new modules with typical modules, which I use.
solr is as search installed. Solr config provides an option to hijack the core search. solr depends on the core search module.
When I use a the drupal search block the redirect goes to /search/node and not to /search/apache_solr
Comment #3
jdanthinne commentedCan you try this patch?
I really don't know if it's going to work, but it tests if apachesolr_search is enabled and then redirects to /search/apache_solr instead of /search/node.
Comment #4
bennos commentedthe redirect works.
posted the wrong URL.
Right is /search/apachesolr_search
To make it complete, you should add also a detection for Lucene API Search.
Comment #5
jdanthinne commentedHere's the corrected patch.
Can you tell me which url is used by Lucene API Search?
Comment #6
jdanthinne commentedRight, I've corrected the solr url, and managed to install Lucene API and made the changes to custom_search to work well with both.
Commited to DEV.
Comment #7
bennos commentedLucene API uses
search/luceneapi_node
as URL.
An other question about Form_state. Hope you can help.
It is a redirect form a normal search box to a views constructed search.
I want to construct via form state redirect following URL.
jobsearch?key=key1
can you help?
thx
Comment #8
jdanthinne commentedYes, I had already found for Lucene API.
For your other question, I don't really understand what you mean…
Can you be more precise please (a screenshot with annotations?) ?
Comment #9
bennos commentedhi
I have a view with an exposed search filter.
A search with the view, creates an URL like this www.domain.com/jobsearch?key=searchkey1234
For this specific use case, I want to change the redirect url to
www.domain.com/jobsearch?key=searchkey1234
the form state
$form_state['redirect'] = 'jobsuche?key='. $keys;
produces a lot of errors.
Comment #10
jdanthinne commentedI begin to understand...
Can you tell me which errors you get?
Comment #11
jdanthinne commentedComment #12
bennos commentedwhite page, ah wsod, nothing in the watchdog. haven't looked in the apache error log.
Comment #13
jdanthinne commentedHi,
I've added a setting "Force search path", where you can enter the path you want.
Download the latest DEV version (from 2010-Apr-06 +) and just try to enter the path "jobsearch?key=[key]" and tell me if it's working the way you want.
Comment #14
jdanthinne commentedNB: DEV version released sooner than expected. You can test with 2010-Apr-05.
Comment #15
bennos commentedthx. will try it out.
Comment #16
jdanthinne commented