Has this behavior changed in the most recent version? If so, how can I set the default keyword search behavior for multiple search terms to AND them together?
For example, if I enter "how to land a helicopter in autorotation"* (no quotes) in the keyword search box, it now returns results as if I had entered "how OR to OR land OR a OR helicopter OR in OR autorotation", whereas previously it returned results as if I had entered "how AND to AND land AND a AND helicopter AND in AND autorotation".
Thanks,
cubbtech
*This was an actual search query on our site. Mining your watchdog logs can provide some amusing fodder for null-set search queries :)
Comments
Comment #1
David Lesieur commentedNo intentional change to the behavior has been made, but I noticed a bug that could lead to such results when running on PHP 4 and using a view to show results. Does that correspond to your setup?
Comment #2
john bickar commentedNo, we're on PHP 5, and not using Views to display results.
Is there a way to set this default in the admin interface? I wasn't able to find it.
Comment #3
David Lesieur commentedGetting OR instead of AND is a bug. There is no admin setting for this, since AND is always implicit, unless searching for a phrase or unless 'OR' is explicitly typed in between the words.
Comment #4
john bickar commentedThanks for the update. Some more information:
I get different search result sets for each of the following searches (no quotes):
So it doesn't look like it's exactly defaulting to the OR behavior, either.
Let me know if I can provide more information. (Site link, for reference.)
Thanks!
Comment #5
David Lesieur commentedThanks for the additional info, this is very helpful!
I think I've found the issue. Faceted Search does not seem to handle the short words (less than 3 characters) properly. I'll look into this...
Comment #6
David Lesieur commentedJust committed a change that (hopefully!) fixes this. Feel free to re-open the issue if you find other problems with short words.
Comment #7
David Lesieur commentedComment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #9
john bickar commentedReopening as this issue still persists for me in both 5.x-1.x-dev and 5.x-1.0-beta4.
(Reference link.)
Comment #10
john bickar commentedAppears to be fixed in 1.0-beta4. Thanks!