wordfence skips scan file changes
-
the “file changes” scan part contains a locked symbol and is not processed in the scan. I thank those who try to help me right now
-
Hi @sushicru, thanks for your message.
When you say ‘locked symbol’ do you mean a yellow triangle? If so, it’s because of scan results involving:
- Scan wp-admin and wp-includes for files not bundled with WordPress
- Scan plugin files against repository versions for changes
- Scan theme files against repository versions for changes
- Scan core files against repository versions for changes
If you get a red stop symbol, you would have to disable the following in Wordfence > Scan > Manage Scan:
- Scan core files against repository versions for changes
- Scan theme files against repository versions for changes
- Scan plugin files against repository versions for changes
- Scan wp-admin and wp-includes for files not bundled with WordPress
You can read more about the scan stages here: https://www.wordfence.com/help/scan/#scan-stages
Thanks,
Peter.
After resetting the firewall settings of wordfence, by recommendation of the plugin, the scan in the part of “file changes” is no processed and ,is displaying a blocked symbol, like represented below.
I have already uninstalled the plugin deleting the corresponding tables in the database and also deleted the wflogs folder (in the wp-content directory) and after reinstalling the plugin again the error persists.
_______________$$$$$$$$$$
__________$$$$$$$$$$$$$$$$$$$$
_______$$$$$$$$$$$$$$$$$$$$$$$$$$
_____$$$$$$$$$______________$$$$$$$
____$$$$$$$_________________$$$$$$$$
___$$$$$$_________________$$$$$$_$$$$
__$$$$$__________________$$$$$$$$$$$$$
_$$$$$__________________$$$$$$$$$$$$$$$
$$$$$_________________$$$$$$$$$_____$$$$
$$$$________________$$$$$$$$$________$$$
$$$$______________$$$$$$$$$__________$$$$
$$$$____________$$$$$$$$$____________$$$$
$$$$__________$$$$$$$$$______________$$$$
$$$$________$$$$$$$$$$_______________$$$$
$$$$______$$$$$$$$$__________________$$$$
$$$$$__$$$$$$$$$$____________________$$$$
_$$$$$$$$$$$$$$$$___________________$$$$
__$$$$$$$$$$$$____________________$$$$$
__$$$$$$$$$$$____________________$$$$$
____$$$$$$$$___________________$$$$$$
_____$$$$$$$_________________$$$$$$
_______$$$$$$$$$$_______$$$$$$$$$
_________$$$$$$$$$$$$$$$$$$$$$$
_____________$$$$$$$$$$$$$$Hi @sushicru, thanks for the extra information.
Just to confirm, have you reenabled the 4 settings I mentioned in Wordfence > Scan > Manage Scan?:
- Scan core files against repository versions for changes
- Scan theme files against repository versions for changes
- Scan plugin files against repository versions for changes
- Scan wp-admin and wp-includes for files not bundled with WordPress
If those are unchecked, they result in the symbol you’re seeing.
Thanks,
Peter.
Hello @wfpeter, when i tried to enable the suggested options and started the scan the settings were disabled again. I wanted to re-enable this option because wordfence was returning unusual critical alerts after an update, and I believed that if this “error” was adjusted, the scan would normalize. It happened that my website was infected with a Trojan (Trojan horse) and this was damaging the wordfence settings. After cleaning the site the wordfence plugin returned to work correctly. In any case I thank you for your support!
The topic ‘wordfence skips scan file changes’ is closed to new replies.