We've implemented faceted search on a multilingual site using i18n. Somehow, there are no search results shown when a visitor is using the non default language. Is it possible to remove the language restriction in a similar way as one can do in views with the filter "Internationalization selection: All content. No language conditions apply."
eg
http://www.domain.com/nl/faceted_search/results/labrador+content_type%3a... OK (nl is default language)
http://www.domain.com/fr/faceted_search/results/labrador+content_type%3a... EMPTY
Note: learning from your feedback on an other post, I believe that by redoing our search results page with a views integration, we can probably address most of our issues
Comments
Comment #1
David Lesieur commentedMmmh, that's unexpected... We might have to look at the SQL queries to understand what is happening.
Comment #2
ThePickwickProject commentedI was wondering if I'm the only one with this issue?
In fact, I just had a look at the SQL and I noticed that some temporary tables are created (causing MySql to run slow). In the sql, you will see that there are some filters on the language that restrict it to the default language "nl" or "no language":
CREATE TEMPORARY TABLE temp_faceted_search_nids SELECT n.nid AS nid,
SUM(i.score * t.count) AS relevance, COUNT(*) AS matches FROM
drupalnode AS n INNER JOIN drupalsearch_index AS i ON n.nid = i.sid
INNER JOIN drupalsearch_total AS t ON i.word = t.word LEFT JOIN
drupali18n_node i18n ON n.nid = i18n.nid WHERE (i18n.language ='nl' OR
i18n.language ='' OR i18n.language IS NULL) AND ( ((n.status = 1) AND
(i.word = 'hond' OR i.word = 'staande') AND (i.type = 'node')) ) GROUP
BY nid ASC HAVING ((COUNT(*) >= 2)):
Comment #3
David Lesieur commentedI'm not sure if it would solve the issue, but you might want to try Faceted Search 1.0-beta4. The queries have improved a lot in 1.0.
Comment #4
David Lesieur commentedQueries have changed a lot since that bug report. Assuming this to have been fixed.