Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to disable categories #1019

Closed
mskf1383 opened this issue Mar 27, 2022 · 5 comments
Closed

Option to disable categories #1019

mskf1383 opened this issue Mar 27, 2022 · 5 comments
Labels

Comments

@mskf1383
Copy link

There are a lot of categories and I don't want all of theme. There must be an option to disable unusable categories.

@return42
Copy link
Member

@mskf1383
Copy link
Author

I mean an options for users, not admins.

@return42
Copy link
Member

return42 commented Mar 27, 2022

IMO serving categories is up to the instance.

There are a lot of categories and I don't want all of theme.

If there are no good reasons for your request I have not thought of yet, I vote to close this issue.


In general I hesitate to personalize the UI more and more / personalization always goes hand in hand with the loss of privacy and makes the UI and the implementation more complex.

We have a lot of preferences a user can set right now, while I assume only 1% of the user base personalize their preferences.

@aleex5
Copy link

aleex5 commented Mar 27, 2022

searx already had this feature, when you deactivate all the engines of a category, this category disappeared, but searxng in some of the updates lost this function.

@return42
Copy link
Member

@aleex5 it isn't really what the opener asks for. What you point out is an issue, to not to mix issues and new features I opened #1020 / thanks for pointing out 👍

return42 added a commit to return42/searxng that referenced this issue Jul 23, 2022
When using ``use_default_settings: true``, removing default categories from
settings.yml will not remove them from the UI.

The value ``categories_as_tabs`` is a dictionary type (a4c2cfb) and dictionary
types are merged additive by ``settings_loader.update_settings()``.

This patch replaces the default ``categories_as_tabs`` by the one from the
``user_settings``.

Related: searxng#1019 (comment)
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
return42 added a commit to return42/searxng that referenced this issue Jul 23, 2022
When using ``use_default_settings: true``, removing default categories from
settings.yml will not remove them from the UI.

The value ``categories_as_tabs`` is a dictionary type (a4c2cfb) and dictionary
types are merged additive by ``settings_loader.update_settings()``.

This patch replaces the default ``categories_as_tabs`` by the one from the
``user_settings``.

Related: searxng#1019 (comment)
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
return42 added a commit to return42/searxng that referenced this issue Jul 24, 2022
When using ``use_default_settings: true``, removing default categories from
settings.yml will not remove them from the UI.

The value ``categories_as_tabs`` is a dictionary type (a4c2cfb) and dictionary
types are merged additive by ``settings_loader.update_settings()``.

This patch replaces the default ``categories_as_tabs`` by the one from the
``user_settings``.

Related: searxng#1019 (comment)
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
return42 added a commit to return42/searxng that referenced this issue Apr 3, 2023
When using ``use_default_settings: true``, removing default categories from
settings.yml will not remove them from the UI.

The value ``categories_as_tabs`` is a dictionary type (a4c2cfb) and dictionary
types are merged additive by ``settings_loader.update_settings()``.

This patch replaces the default ``categories_as_tabs`` by the one from the
``user_settings``.

Related: searxng#1019 (comment)
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants