Hi @delanthear, thanks for getting in touch.
It has been known for a scan to start running around the same time as automatic/manual plugin updates are performed, so picks up the outdated plugins at the start but won’t realize plugins have been updated by the time it ends.
Sometimes re-running a full scan rather than a quick scan could resolve update discrepancies such as this too. It is also known for plugin developers to occasionally make a very minor update and not increment the version number of their plugin. This should also get spotted and updated when our servers check for latest plugin repository versions, but this happens at set intervals during the week so can appear modified for up to 48 hours, which could be less depending on timing of the scans.
Let us know here if this notice doesn’t disappear within a few days.
Thanks,
Peter.
This really smells like a bug in your scanning. I’ve received a number of these now across different sites where it warns about a missing update to the same version.
Surely the check should verify that the email it is about to send makes sense before sending it? Perhaps it should redo the check on the plugin version numbers before it sends the email. It spooks our customers when they receive nonsensical warning messages from the plugin that we’ve told them to trust :/
I don’t know if this makes a difference, but the plugin that’s generating the error is Astra Pro. The email has this on it:
* The Plugin “Astra Pro” needs an upgrade (4.1.4 -> 4.1.4).
https://wpastra.com/pricing/?utm_source=graupi-license-form&utm_medium=graupi-license-invalidation&utm_campaign=purchase-astra/#developers
NOTE: You are using the free version of Wordfence. Upgrade today:
However, the plugin is licenced and marked as such. Is there a reason why it’s linking the the paid for version?
-
This reply was modified 3 years, 2 months ago by
delanthear.
