searxng/docs/admin/settings/settings_ui.rst, branch custom

[mod] client/simple: client plugins (#5406)

2025-12-02T10:18:00Z

* [mod] client/simple: client plugins Defines a new interface for client side *"plugins"* that coexist with server side plugin system. Each plugin (e.g., `InfiniteScroll`) extends the base `ts Plugin`. Client side plugins are independent and lazy‑loaded via `router.ts` when their `load()` conditions are met. On each navigation request, all applicable plugins are instanced. Since these are client side plugins, we can only invoke them once DOM is fully loaded. E.g. `Calculator` will not render a new `answer` block until fully loaded and executed. For some plugins, we might want to handle its availability in `settings.yml` and toggle in UI, like we do for server side plugins. In that case, we extend `py Plugin` instancing only the information and then checking client side if [`settings.plugins`](https://github.com/inetol/searxng/blob/1ad832b1dc33f3f388da361ff2459b05dc86a164/client/simple/src/js/toolkit.ts#L134) array has the plugin id. * [mod] client/simple: rebuild static

[fix] cleanup: rename `searx` leftovers to `SearXNG` (#5049)

2025-07-26T04:22:46Z

Signed-off-by: Markus Heiser

[mod] remove option ui.static_use_hash (cache busting) (#5004)

2025-07-11T14:53:36Z

Cache busting has caused serious problems for users in the past, here are two examples: - https://github.com/searxng/searxng/issues/4419 - https://github.com/searxng/searxng/issues/4481 And it makes development and deployment significantly more complex because it binds the client side to the server side: - https://github.com/searxng/searxng/pull/4466 In the light of a decoupled development of the WEB clients from the server side: - https://github.com/searxng/searxng/pull/4988 is it appropriate to abandon this feature. In fact, it has been ineffective since #4436 anyway. However, the benefit has always been questionable, since at best only a few kB of data are saved (at least in the context of an image_proxy, the effect is below the detection limit). Ultimately, the client is responsible for caching. Related: https://github.com/searxng/searxng/issues?q=label%3A%22clear%20browser%20cache%22 Closes: https://github.com/searxng/searxng/pull/4466 Closes: https://github.com/searxng/searxng/issues/1326 Closes: https://github.com/searxng/searxng/issues/964 Signed-off-by: Markus Heiser

[web-client] integrate the migrated theme in the development workflows

2025-02-28T11:27:41Z

Signed-off-by: Markus Heiser

[feat] search: add url formatting preference

2024-12-01T12:08:50Z

[feat] simple theme: pure black theme style

2024-10-03T08:53:17Z

[feat] docker: add env vars for common public instance settings

2024-06-14T12:58:02Z

[mod] add hotkeys option to settings.yml

2023-10-09T16:13:00Z

The change in the hotkey mechanism introduced in 317db5b04 does not allow configuration via `settings.yml`. This commit adds that functionality. Closes: #2898

[feat] search on category select without JS

2023-09-18T19:29:11Z

Co-authored-by: Alexandre Flament

[fix] typos in documentation & messages

2023-08-13T06:50:29Z