Open dterhorst opened 2 months ago
This build artifact should have these changes, if you don't want to wait for an official build:
https://github.com/RupertAvery/DiffusionToolkit/actions/runs/8773444541/artifacts/1433316835
Latest builds will appear in https://github.com/RupertAvery/DiffusionToolkit/actions. Click on the workflow run and scroll down to the artifacts and download DiffusionToolkit.
Describe the bug If you right-click on an image that has
.txt
metadata and choose the Move option, the.txt
metadata is not moved with the image.Version: v1.6.1
To Reproduce
example
.example/example.jpg
andexample/example.txt
. The content shouldn't matter.example/destination
folder.example
folder.example/destination
and press "Select Folder"Expected behavior
example/destination
should contain bothexample.jpg
andexample.txt
.example
should not containexample.txt
.Actual behavior
example/destination
containsexample.jpg
, but notexample.txt
.example
containsexample.txt
.Screenshots
![20240416010503](https://github.com/RupertAvery/DiffusionToolkit/assets/100437146/27e98529-9116-4f36-8d5f-a7bcb16812af)
Additional context Diffusion Toolkit strongly encourages you to manage files from within the app. If you manage files manually from outside the app, the database gets out-of-date and the images appear "Unavailable" inside the app. Messing with
.txt
metadata can force you to execute a costly "Rebuild metadata."That, in combination with this bug, leads to a worst-of-both-worlds scenario where you have to manage some files from within the app, but then manually track down their original location anyway to move the metadata by hand. (Assuming you even notice the problem occurred.)
I am using Diffusion Toolkit to manage over 100k images, spread across countless directories. If I moved a batch of a hundred images at a time, it would be daunting to even think about guessing where they all came from so I could fix orphaned metadata one-by-one.