Pausing Wordfence when updating WordPress

  • Resolved Miroslav Glavi?

    (@miroslavglavic)


    6 days, 17 hours ago

    I don’t know if this is normal or I didn’t notice……but ever since I updated my sites (5 of them) to 6.7…I’ve been getting the files changed prompt. Over 2,500 files changed.

    Obviously core, and even 2024 were changed, it’s an update.

    I don’t know if it’s possible to turn off Wordfence, or tell it that those changes is normal, it’s WordPress 6.6.2 or whatever to 6.7 changes.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @miroslavglavic, thanks for getting in touch.

    There’s no need to pause or disable Wordfence. The issue happened on Wednesday and was due to the process that mirrors new core releases not completing normally and stopping halfway. The issue was fully resolved soon after, we have additional alerting in place in case it occurs again and we’re refactoring the code that runs this process to make it far more robust.

    Subsequent automatic or manual scans should no longer show the files as unknown. We have some documentation on these scan results here in general for reference, and restoring deleted or repaired files from a backup if the site has issues is the best option: https://www.wordfence.com/help/scan/scan-results/#unknown-file-in-wordpress-core

    Please also check the following topic: Check or Subscribe to the Wordfence status updates

    Many thanks,
    Peter.

    Thread Starter Miroslav Glavi?

    (@miroslavglavic)

    Thank you for the reply.

    One thing: it would be nice for Wordfence to know when I am updating. Obviously there are file changes whenever there is an update for core, theme or plugins. I do my updates manually (myself).

    I just checked Wordfence on all my sites and there are 2 notifications….there are 2 plugins needing updates. I updated them and that is it. So the issue got resolved.

    Plugin Support wfpeter

    (@wfpeter)

    Wonderful that it’s resolved for you @miroslavglavic, we’ll keep your feedback around manual updates in mind although the failed mirror of core files at our end does sound like the reason 2,500 files were detected rather than the way you updated the site in this case.

    Peter.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.