Scanner: exclude directory recursively

  • Resolved Barcelo

    (@barcelo)


    3 years, 4 months ago

    Q: what is the correct way / schema to recursively exlude a directory (complete sub-content!) from beeing scanned by the scanner?

    F.e.: if I just add wp-content , this is totally ignored!

    So what is the right schema?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    3 years, 4 months ago

    Hi@barcelo,

    Yes, just adding wp-content should work all path relative to ABSPATH

    (root folder of wordpress install) should work as general.

    Do your server is windows?

    Thread Starter Barcelo

    (@barcelo)

    3 years, 4 months ago

    Hi @hjogiupdraftplus ,
    thank you – nope, no Windows server – Linux server.
    I will re-check that again with some testing on differnent Linux servers and might get back to you.

    chillstarr

    (@chillstarr)

    3 years, 4 months ago

    I think there should be some more/ better examples in the GUI’s help.

    At the moment it gives the examples:
    cache/config/master.php
    somedirectory
    Which doesn’t give us too much to go on.

    I’m on a Linux/ Apache server and In the file change detected emails, it gives complete filesystem paths e.g:
    /home/username/domain.com/wp-content/aiowps_backups/index.php

    But if you add:
    /home/username/domain.com/wp-content/aiowps_backups
    it doesn’t ignore that directory.

    I think I’ve finally got this working by using paths in this format:
    wp-content/aiowps_backups
    (without a slash at the start or end)

    HTH

    • This reply was modified 3 years, 4 months ago by chillstarr. Reason: Missed word
    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    3 years, 4 months ago

    Hi @chillstarr

    Thanks for your input, I will create internally a ticket for this.

    Regards

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Scanner: exclude directory recursively’ is closed to new replies.