mirror of
https://github.com/ilyakooo0/searx.git
synced 2024-11-29 10:42:18 +03:00
[fix] use engine-type when looking up supported_languages from JSON files
searx/data/engines_languages.json stores language information for several searchengines in a json endoded dict that maps engine-"types" to their supported languages; for instance there is an entry "google", mapping to the supported languages of the google engine. However, the lookup code did not use the engine 'type' (as in: the filename searx/engines/<enginetype>.py), but instead the manually configured engine name from settings.yml when querying. This is problematic as soon as users start to specify additional engine instances with custom names in the config file, as for instance suggested as a workaround for multilingual search in the manual[0]: > engines: > - name : google english > engine : google > language : english Here, the engine name "google english" will be used for the lookup in the json file, which does not exist. The empty supported_languages then lead to a type error later in the processing callchain. This patch changes the behaviour to use the engine's entry-"type" ("google" in the above example) for the lookup. This should fix bug #2928. 0: https://searx.github.io/searx/user/search_syntax.html#multilingual-search
This commit is contained in:
parent
49b2553561
commit
23d6c9c798
@ -108,8 +108,8 @@ def load_engine(engine_data):
|
||||
sys.exit(1)
|
||||
|
||||
# assign supported languages from json file
|
||||
if engine_data['name'] in ENGINES_LANGUAGES:
|
||||
setattr(engine, 'supported_languages', ENGINES_LANGUAGES[engine_data['name']])
|
||||
if engine_data['engine'] in ENGINES_LANGUAGES:
|
||||
setattr(engine, 'supported_languages', ENGINES_LANGUAGES[engine_data['engine']])
|
||||
|
||||
# find custom aliases for non standard language codes
|
||||
if hasattr(engine, 'supported_languages'):
|
||||
|
Loading…
Reference in New Issue
Block a user