I’m having problems with the Wordfence extension since the beginning. I wonder if it is just me or do others have the same issues. For instance: In the child sites overview table there is an indicator that once showed if there are problems. Nowadays this is only a gray icon with no function.
I used to like it but it had it’s problems in the beginning already. I guess mainly because Wordfence changed a lot in the past. I hope these issues can be fixed. Thanks for reading
I seem to be having a similar issue here. On the Wordfence Dashboard tab I get a red status shield for my website. When I click on the shield all the scan stages show grey / icons. How can I see the issues related to the scan results? In Wordfence Central the scans displays correctly. I really want to be able to use this Extension instead of Wordfence Central, is it sometihng I am doing wrong or is the Wordfence Extension just buggy?
Also, now in the Wordfence Dashboard I select all the child sites then click the “Scan all Child Sites” green button and get an error saying “Please select websites to scan” even though the sites are selected… Thought?
The extension simply does not work. And I have several issues open. It should be discontinued until fixed or be removed permanently. I have the same problems as you mentioned.
Hmm, the icons in the sites overview table are still gray and individual site scans still fail to start. The according button in the menu with the three dots has no function. The bulk actipons menu now lacks the start scan option. Furthermore still no results are shown in the results table. The “ignored results” table works though (but i am not quite sure if this worked before).
Update: In some cases results ARE shown. It is this at least this type of error that is never reflected on the child sites results overview page though:
Type: Skipped Paths
5 paths were skipped for the malware scan due to scan settings
Can you please try to clear all cache, and maybe try to deactivate non-MainWP plugins temporarily to see if there is some conflict on your setup. If non of this helps, I would really like our dev team to check this further, please feel free to open a helpdesk ticket so we can check this further.