@qymab @return42

Thank you. It is working now again, but only when activated via web interface (../preferences).

Is it possible to activate in settings.yml for everybody?

Thank you in advance.

settings.yml:

enabled_plugins:
  - 'Hostnames plugin'

used to work, but appears to be broken since edfbf1e?

FYI: hostnames plugins works as implemented (what might differ to what is expected) ..

You need to manually enable this in Preferences.

yes 👍 .. so what have changed? .. hostname plugin was off by default (from the beginning on):

but ..

used to work, but appears to be broken since edfbf1e?

Nope .. its not broken .. it is fixed in the PR you link .. in the past, this default_on was switched to True

when a plugin was listed in the enabled_plugins: (internal) section

But this was an issue in my eyes .. TBH we have more than the on/off states

a. "plugin is not enabled" --> not available for the user (not listed in the preferences of the UI)
b. "plugin is enabled" --> user can activate the plugin in the preferences (opt-in) / what is the case for the hostnames plugins
c. "plugin is enabled and active by default" --> user can de-activate the plugin in the preferences (opt-out)

Before PR:

• [refactor] typification of SearXNG (initial) / result items (part 1) #4183

we had a. and c. (opt-out) .. after the PR we have a. and b. (opt-in) .. personally I prefer opt-in in a two state switch (default_on True/False) ..

We can consider to have a switch with three states e.g.:

• bool(default_on) --> Where False is a. and True is b.
• default_on == "opt-in" --> equal to default_on == True (b.)
• default_on == "opt-out" --> implements the missing c.

If you see a need in a "switch with three states" please open a feature request.