-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Scan active plugins #3
Comments
+1 for the general idea. Regarding false positives etc: I can’t help but seeing a potential boost in support requests. Regardless whether we could indicate that scanning plugins is “experimental”, I see a good chance we’d soon have plugin authors hammering our doors because of users hammering theirs due to existing or non-existing problems detected by AntiVirus. This is not to say I’m against further testing the idea, I like it! Let’s just also think of possible implications within the ecosystem. |
Yep, that's what I was thinking about too. If this works out, we could do something like this in the beginning:
But first, |
📷 😉 |
Other areas that may be worth considering for a scan:
|
Additionally, we could tell the user something like "Hey, we detected you have 6 inactive plugins. Better delete them!" |
I think we shouldn't just limit this functionality to the active theme.
Any objections about such a feature? I'm sure it will require some work to achieve this. Maybe it's not even easily possible, e.g. because there could be many false-positives with some plugins.
The text was updated successfully, but these errors were encountered: