-
-
Notifications
You must be signed in to change notification settings - Fork 186
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
ARPSCAN, INTRNT, PHOLUS plugins can't be unloaded #726
Comments
This should be fixed in the next release. Please have a look at the newest Make sure you refresh your browser cache - and click the 🔄 refresh button in the top right corner. It would be great if you could test this (backup everything first or use a new container) on your end and letting me know if the issue was resolved. Thanks in advance, PS. Thank you for the donation ♥ |
Just pulled a new update and issue has been fixed. I tested multiple time disabling and unloading the plugins and they did not reappear. Thanks |
Thanks for checking 👍 |
Releasing -> closing |
Is there an existing issue for this?
Current Behavior
Enabled Settings keep reappearing after disabling
For example, I have disabled Internet Check, Pholus and Arp-Scan and then un-selected the plugin from the list, Save. They go away.. Then when i make a different change and hit save again, i see a box saying warning, importing settings and they all come back. (Settings imported: 05/07/2024, 18:02:30)
Expected Behavior
Once disabled and removed, dont come back
Steps To Reproduce
Enabled Settings keep reappearing after disabling
For example, I have disabled Internet Check, Pholus and Arp-Scan and then un-selected the plugin from the list, Save. They go away.. Then when i make a different change and hit save again, i see a box saying warning, importing and they all come back. I have even deleted the docker image and re-configured it all (Dev) and same issue.
app.conf
No response
docker-compose.yml
No response
What branch are you running?
Dev
app.log
No response
Debug enabled
The text was updated successfully, but these errors were encountered: