Hi @nppbc,
If you’ve re-run a full scan rather than a quick scan, I would expect any update discrepancies to have been resolved. It is also possible sometimes for plugin developers to make a 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 at wordpress.org, but this happens at set intervals during the week so can appear as modified until then.
I believe our servers are due to update again today, so if this still persists in around 24 hours from now, please drop me a copy of your diagnostic report so I can take a look at the file in question from your scan results. You send the report to wftest @ wordfence . com by finding the link at the top of the Wordfence > Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.
NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email
Thanks,
Peter.
Thread Starter
nppbc
(@nppbc)
It popped up again so I’m sending the report.
Thanks
Hi @nppbc, thanks for sending your diagnostic over.
I only have a “Scan Issues” result in there about the difference between WordPress core’s installed version (5.9.3) compared to the available version of 6.0
I feel that if a further plugin discrepancy notice hasn’t been dismissed automatically with subsequent scans, you should be safe to select “Ignore” on this as it’s no longer coming through with your most recent scan results. Although, in time our repository and WordPress.org’s repository versions may have synchronized.
Let me know if that hasn’t worked. Feel free to share a screenshot with a service like Snipboard if you can see something that isn’t showing in the diagnostic report’s scan results.
Peter.
