Viewing 4 replies - 1 through 4 (of 4 total)
  • Hello graftedin,
    it depends a bit on the context whether an issue is considered “critical” or “warning”. Here are some examples of “Critical” situations:

    * File contains suspected malware URL
    * This file appears to be installed by a hacker to perform malicious activity
    * File is an old version of TimThumb which is vulnerable
    * File contains suspected phishing URL
    * Theme or plugin needs to be updated for security

    Warnings may be what looks to be safe changes to files that you should still inspect or that a password is not complicated enough.

    The purpose of being able to choose it to allow people to limit the amount of emails they get from Wordfence. I suggest you start with both on. That way you can get to know the warnings a bit before you choose to ignore any of them.

    Thread Starter graftedin

    (@graftedin)

    Thanks for your response.

    What “alert” do I need to turn off so it quits complaining to me that other plugins are out of date?

    Hello graftedin,
    Those will be critical issues so you would have to deselect critical notices. There is an alternative though. To force Wordfence to ignore particular issues you can run a scan and then scroll through the results and click “Ignore this issue” for each issue that you want to ignore.

    Thread Starter graftedin

    (@graftedin)

    Thanks. Can I suggest that you create and option to opt out of out of date warnings for plugins and themes.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Warnings vs Critical Problems’ is closed to new replies.