Describe the bug
I think the software is checking duplicates wrong or in a wrong order in certain constellations. When it deletes the files from the drive, there is no other version of this file left.
To Reproduce
Steps to reproduce the behavior:
Add for example the whole drive "D:\" -> done
Delete D:\ from software without cleaning database.
2.1. Moving some files around.
Add Sub-folder of D:\ instead of whole drive, because more flexible, e.g. "D\sorted".
Run duplicate check
Expected behavior
The software recognizes the new added scenes as "duplicates", deleting either the new ones or the old ones, but leaving none in the process, resulting in a data loss.
Recommendation besides looking into the feature again: Safety measure: moving to trash bin instead of deleting them completely.
Here a screenshot of my now empty folder for the lulz. :D
A fix will be implemented in develop during the weekend. The fix will be done this way:
Match the iteration1 scene with the iteration2 scene. If the absolute paths to the files are the same (ie. same file), then the dupechecker will break the iteration and carry on.
Describe the bug I think the software is checking duplicates wrong or in a wrong order in certain constellations. When it deletes the files from the drive, there is no other version of this file left.
To Reproduce Steps to reproduce the behavior:
Expected behavior The software recognizes the new added scenes as "duplicates", deleting either the new ones or the old ones, but leaving none in the process, resulting in a data loss.
Recommendation besides looking into the feature again: Safety measure: moving to trash bin instead of deleting them completely.
Here a screenshot of my now empty folder for the lulz. :D