We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Open below pages in two separate tabs and keep them opened https://xxx.xxx.xx.xxx/#filters https://xxx.xxx.xx.xxx/#logs
Block any domain name using 'block' button on query log page then go to filters page and refresh, you'll see it updated under 'custom filtering rules'
Write any domain names on 'custom filtering rules' field then click apply. If necessary refresh the page to ensure it applied as well
Go to query log page again and block a domain name
Then go back to filters page and refresh, you'll see all manually written domain names erased (means from .yaml file)
(It doesn't occur when perform that task within single tab)
AdGuard Home v0.98.1 | Windows
The text was updated successfully, but these errors were encountered:
Related but not duplicate #2374
Sorry, something went wrong.
Tbh I think this IS duplicate and will be solved automatically if #2374 is implemented.
No branches or pull requests
Steps to Reproduce
Open below pages in two separate tabs and keep them opened
https://xxx.xxx.xx.xxx/#filters
https://xxx.xxx.xx.xxx/#logs
Block any domain name using 'block' button on query log page then go to filters page and refresh, you'll see it updated under 'custom filtering rules'
Write any domain names on 'custom filtering rules' field then click apply. If necessary refresh the page to ensure it applied as well
Go to query log page again and block a domain name
Then go back to filters page and refresh, you'll see all manually written domain names erased (means from .yaml file)
(It doesn't occur when perform that task within single tab)
AdGuard Home v0.98.1 | Windows
The text was updated successfully, but these errors were encountered: