mirror of
https://github.com/benbusby/whoogle-search.git
synced 2026-04-26 04:35:54 +03:00
[GH-ISSUE #73] [BUG] Cannot set search to 'any language' #50
Labels
No labels
Fixed (Pending PR Merge)
Stale
bug
enhancement
enhancement
good first issue
help wanted
keep-open
needs more info
pull-request
question
theme
unfortunate
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/whoogle-search#50
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @totti4ever on GitHub (May 24, 2020).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/73
Describe the bug
After setting the language in the config to German the results are always in German, I cannot go back to 'any language', it just flips back to German.
To Reproduce
Steps to reproduce the behavior:
any languageDeployment Method
runexecutableVersion of Whoogle Search
Desktop (please complete the following information):
@benbusby commented on GitHub (May 24, 2020):
Fixed by
3dbe51e9e7. All language configuration should be handled by the Whoogle search home page from now on, the config card on the results page was a leftover element that should've been removed. The Docker Hub image should be updated shortly. Thanks for reporting!@totti4ever commented on GitHub (May 24, 2020):
@benbusby thanks for the quick response and fix. But I am somewhat disappointed, since I am having two main use cases:
Problem now is, I have to decide and switch based on the decision the main configuration. I thought, it was a really good solution to offer the selection of primary language only and all languages in the results page. What were your intentions of removing it?
@benbusby commented on GitHub (May 25, 2020):
The language switcher you were referring to originally never worked in the first place, it was a leftover element of the UI that needed to be removed to avoid confusion. Adding in the functionality you’re seeking would be an entirely separate feature (that hasn’t existed before), which I’m happy to add. I’ll create an issue for it shortly.
@qubit999 commented on GitHub (Jan 1, 2022):
This issue was not solved. I have the same issue here using the latest docker image.