problem with file exclusion

  • Resolved wpo-HR

    (@wpo-hr)


    1 week, 4 days ago

    Hi, I have many galleries with thousands of images, where images are stored in compressed form as image.jpg and partly in original uncompressed form as image.jpg_backup.

    In a normal daily website backup I exclude all backup files (.jpg_backup), which works fine.
    In a weekly backup I want to just save the backup files but exclude the corresponding compressed .jpg files. However, specifying .jpg as an exclusion criterion will not only exclude the .jpg files as desired but also the .jpg_backup files.

    Is there a possibility to specify the exact file type (.jpg) as an exclusion criterion?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Ov3rfly

    (@ov3rfly)

    1 week, 3 days ago

    The comparison is matched anywhere in the filename path.

     if (stripos((string) $path, $exclusion) !== false && !empty($exclusion)) {

    The entry form says “Add folders, files or extensions you want to exclude” but the code does not handle extensions as such.

    With your exclusion .jpg also filenames like whatever.jpgreat.file.txt are excluded.

    Internally also other filename parts are added to exclusion list:

    $this->exclude_from_backup = array_merge(
    	$this->exclude_from_backup,
    	[ '.tmp','.svn','.git','desktop.ini','.DS_Store','/node_modules/' ]
    );

    So also filenames like whatever.github.thing.txt or some.desktop.initialized.thing.txt are excluded.

    Would consider this as a bug as it can cause severe side effects with incomplete backups.

    Plugin Support BackWPUp Support

    (@saranshwpm)

    1 week, 2 days ago

    Hi,

    Thanks for your detailed explanation!

    You’re absolutely right—at the moment, our file exclusion system doesn’t apply exact extension logic. So when you exclude .jpg, it also affects files like .jpg_backup, which is why you’re seeing this behavior in your weekly backup setup.

    That said, we’ve raised this as a feature request to our development team, and hope to support more precise exclusion filtering in a future update.

    Thanks again for the thoughtful feedback!

    Ov3rfly

    (@ov3rfly)

    1 week, 2 days ago

    Why has this issue been marked as “resolved”? It clearly isn’t resolved and it also isn’t some feature request for some development team. It is a serious bug.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.

Tags