FileSieve 4

  • Status Closed
  • Percent Complete
    100%
  • Task Type Bug Report (major)
  • Category Backend / Core
  • Assigned To
    Joseph Cox
  • Operating System All
  • Severity Critical
  • Priority Very High
  • Reported Version 4.35
  • Due in Version 4.36
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: FileSieve 4
Opened by Joseph Cox - 27 February 2018
Last edited by Joseph Cox - 27 February 2018

FS#330 - Overwrite Rules only generating a single rename mask

When FileSieve (FS) encounters a file that already exists in the destination and the user has set some overwrite rules, FS generates a filename based on the entered Rename Mask and tests to see if that exists. If it does, it then generates another name (based on the # code (%file_number% in 4.36); that hash symbol represents a number that is incremented each time an on-disk collision is detected) and tests that.

Due to a bug in 4.35 and earlier (unknown at which point the bug was introduced but it may have been due to some major changes to the engine code - specifically the Prescanning step - so FS can gather additional metadata on files to give plugins more control and flexibility), the first attempt at generating a filename was always successful regardless of if that file existed on-disk.

The reason for this is that it was using the wrong path to check for the file’s existence.

Fixed in 4.36.

Closed by  Joseph Cox
27 February 2018 10:08 AM
Reason for closing:  Fixed

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing