Same happened here on readme files of two plugins. The ‘Tested up to’ number had been backed down. Went to the support forums for those plugins. Compatibility issues were being reported. My guess is that until fixes are in, the developers modified their repository readme files to a lower compatibility, which apparently is something they can do without making it a plugin update (makes sense to me). They probably had good results when testing ahead of the new WP release and then some things went bump for some sites anyway.
I usually update WP right away but this time I did not. The WP 4.6 release reads more like a “new features” update rather than a “security update”. Red flag to me, not in desperate need of new features, let someone else test it. My setup may not have produced the same glitches reported by others but nonetheless happy to not be bothered.
Hope all else is okay with your installs. Myself, marked those WF-flagged readme files as “Ignore until changed”.
Listening though, in case someone else has other ideas.
Wilderbee, I hear you on those stupid endless WordPress “updates.” Best to hold off for a day or two and let everyone else test it.
As for the scans vs readme files, In my case I rename or delete most readme files ASAP. To solve problem with Wordfence, just add readme wildcard pattern to the “Exclude files from scan that match these wildcard patterns” The amount of false positives you otherwise get is clearly not worth the time of dealing with them.
Better, I simply don’t run the comparative scans, in my opinion they’re way too resource intensive and my plugins are all over the map. Some I don’t upgrade because of weirdness, others I modify, and so forth. If I ran the comparison scan I’d get a list a mile long.
Just because security software such as Wordfence has a feature, that doesn’t mean it’s necessary to use it.
MTN
