Feature Request: Don’t make auto-update plugins a problem
-
Hello Humans,
I have a little feature request. Wordfence is flagging a plugin that needs an update a problem. Which is fine.
But it should not flag it a problem when auto-update is enabled and the auto-update has not yet run (because it’s scheduled for in a few hours). Because it’ll turn into a non-problem by then and the mail was sent for nothing.
For example, “Redis Object Cache” got an update tonight. And now I get a ton of mails with new “problems” on the sites which only say Redis needs an update. But by the time I click the Link to WordfenceScan, the auto-update already ran and so it’s no problem at all.
So maybe it could be implemented in a way that Wordfence checks if the plugin needs an update and auto-update is on, and if so, maybe put it into a grace queue, waiting for however many hours (12 maybe?) and check if the version changed as expected. If so, cool. If not, it should raise a problem. Because maybe a license key for a commercial plugin expired or whatever.
Thank you for listening and thank you for your hard work with this plugin :–)
- The topic ‘Feature Request: Don’t make auto-update plugins a problem’ is closed to new replies.