Would it be possible to make Search Autocomplete language sensitive?

In a multilingual site, the list of Search Autocomplete-results contains words from all accessible languages.
However, only results from the active language should be listed.

Side-note: for other users, it might be interesting to know that the module -logically- isn't compatible with the Stemmer modules.

Comments

bonvga’s picture

Assigned: Unassigned » bonvga

Hi,

Relating to the language sensitive, I think it's possible to implement it. Could you confirm to me you are using the i18n module for your multilingual site ?

Concerning the Stemmer module, I haven't the answer actually. But if this module feeds the search_index table, I think it could work.

Arnaud.

beert’s picture

Hi bonvga.

I'm using the Localizer module for the multi-lingual site.

(The stemmer modules indeed feed the search_index table; as a result, the outcome of their algorithms are put into the search_index table. In a general search, a stemmer can be very useful. But in combination with Search Autocomplete, the expanded list of results is 'contaminated' with their algorithm results.)

Sorry it took a while to follow this up; I'm in the middle of a renovation...

Dom.’s picture

Status: Active » Closed (works as designed)

Closed because of 3 years of none activity: this was opened at the time of previous maintainer.

Mutli-language is not yet an objective for the module.

Thanks for the interest you have with this module.
Miro

serans’s picture

Version: 5.x-1.x-dev » 7.x-2.0

I developed a small patch which allows for language-sensitive usage of search autocomplete. Before submitting I want to make sure I have the latest version, but search_autocomplete.install (amongst many other files) is not on the git repository. Am I missing something?

Dom.’s picture

Hi!

Sorry I did not reply earlier, but I had a one week holiday somewhere with no internet (in 2012 can you believe it!).

Anyway: the latest version in the 7.x branch is the 7.x-2.0 version. You can download it from the main module page using the zip link. If you use the git directly, for some reasons, if don't use the tag, it will download you the 5.0 version, no matter which branch you want. I don't know the reason, but I suppose it comes from how the git was created by the previous maintainer, at the time of Drupal 5. Since then, the module was no more used until I took the maintenance. I don't know how to change it, and it's a bit of a mess for me too.

serans’s picture

Assigned: bonvga » serans
Status: Closed (works as designed) » Active

No worries, now it's me who's going on holidays next week (hope I have time to upload something before ;)
If the previous maintainer created the repo at the time of Drupal 5 no wonder some weird stuff happens, I think they used SVN back then and migrations are never painless. I'll use the good'ol zip instead.

Dom.’s picture

Status: Active » Closed (fixed)