Environment
- AdGuard Home
client_v2 (SolidJS migration)
- Any browser
Description
Two bugs in the new client_v2 frontend:
-
Filter update interval resets to 24h. In Settings → Filters, toggling the "Enabled" switch and saving an interval (e.g. 1 hour) works, but the interval silently returns to 24 hours on the next page load / config update. The mount effect in Settings/FiltersConfig posts setFiltersConfig with the default interval before the current filtering status has loaded, overwriting the saved value on the backend.
-
Interval radio labels stay in English after switching language. With the UI language set to Vietnamese (or any non-English locale), the filter update modal's interval radios render English labels ("Disabled", "Every hour", …) while the rest of the dialog is translated. The radio options are built once at module load with the initial locale instead of being re-resolved per current language.
Steps to reproduce
- Open Settings → Filters, enable filtering, set update interval to 1 hour, save.
- Reload the page → interval shows 24 hours again.
- Switch UI language to Vietnamese, open the filter update modal → radio labels remain English.
Expected behavior
- The saved filter update interval persists.
- Modal radio labels follow the current UI language.
Environment
client_v2(SolidJS migration)Description
Two bugs in the new
client_v2frontend:Filter update interval resets to 24h. In Settings → Filters, toggling the "Enabled" switch and saving an interval (e.g. 1 hour) works, but the interval silently returns to 24 hours on the next page load / config update. The mount effect in
Settings/FiltersConfigpostssetFiltersConfigwith the default interval before the current filtering status has loaded, overwriting the saved value on the backend.Interval radio labels stay in English after switching language. With the UI language set to Vietnamese (or any non-English locale), the filter update modal's interval radios render English labels ("Disabled", "Every hour", …) while the rest of the dialog is translated. The radio options are built once at module load with the initial locale instead of being re-resolved per current language.
Steps to reproduce
Expected behavior