[Defender Pro] When to delete vs ignore filescanning?

Can someone clarify for me when to delete and when to ignore a result in the filescanning of Defender?
Ive read to the documents a bit and not sure exactly when to delete things. For example, it currently has an issue with Snapshot, in the base.php.
It says red/green highlighted code but I don’t see any colors in the code so not really sure. All other suspicious files from the filescanning are also from plugins that I know about. Should I just ignore them all? Or can I just delete things?

If I have to ignore, what do I need to lookout for in the filescanning? So when to delete?

Thanks in advance.

  • Ash
    • Code Norris

    Hello Kim

    Defender file scanning system scans all the files and finds the potential codes. But that doesn’t mean all the found codes are harmful. For example, there is an eval() function which is needed in some cases, but this function can also be used for bad purpose. Now, Defender shows when it finds such a function, now you can consult with the plugin author to know its purpose. Also, there are, of course, some trusted vendors that you need not to check with. But for free plugins and some untrusted vendors, you should check with them, check review and then you have to decide you should keep it o or not.

    In our plugins, we always try to avoid using such functions, the notice you saw for snapshot is from a third party library and so we cross checked it before adding into our plugins, no worries about that :slight_smile:

    I hope it helps! Please feel free to ask if you have any more questions regarding this.

    Cheers,
    Ash