• If this was the first time WordFence had done this I would not be posting. But it is not the first time.
    Log in to my blog and check for updates. 3 Themes to update. Select all and update. Then run a scan. Yes that is correct every modified files in the updates is now a WordFence Issue to have to deal with. Yes there is bulk repair but since all of the themes were just updated bulk repair may not be the solution. Wish I could suggest a solution but I don’t have one either. Other than this issue, I have been mostly happy with the WordFence Plugin

    https://wordpress.org/plugins/wordfence/

Viewing 2 replies - 1 through 2 (of 2 total)
  • So you updated the themes via the wordpress admin updates page (like at http://www.sitename.com/wp-admin/update-core.php ) and the issues still show up on the scan results page? Did a new scan result in finding the same problems?

    Thanks!

    tim

    Thread Starter flyfisher842

    (@flyfisher842)

    Yes updated from the WP updates page. Selected all themes and clicked update. After update was done, I did a wordfence scan and get the notices that all the updated pages have changed from the repository. This could be because the repository has not been updated but also could be that WordFence has not downloaded the latest updates to their servers for the scan comparison. (I did not think about this until a couple of days after the post.)

    If I don’t do the repairs, the scan may after a couple of days not show any discrepancies. But mostly I did repairs right away. I think the last time this happened, I just let it sit for a couple days then did a scan and it was ok. So it may be a timing thing about when the repository changes are downloaded to your servers. (At least I would imaging that is how you are doing this comparison check. As I would think WordPress.org would not appreciate WF slamming their servers all the time.

    Lets let it roll for a bit and the next time I have this happen, I will let it alone for a couple days and see if it self corrects.

    But the scan does indeed sometimes show there is a difference between repository and the updated version if scan is done right after update. This is not an every time thing.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘False Positives’ is closed to new replies.