You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used the GitHub search to find a similar issue and didn't find it.
I searched the documentation, with the integrated search.
I already read the docs and didn't find an answer.
I can replicate the issue inside the Demo install.
Homebox Version
0.16.0
What is the issue you are experiencing?
When I create an Item and add a photo or any other attachment, and later delete it, the attachments are not deleted, it is just abandoned inside .data/group-id-code-here/documents. Unless I edit the item and delete the attachments one by one, then it deleted correctly from storage. There should be a lot of attachments that are no longer used lying around in my storage.
I was wondering too why the system maintains a record inside the documents table inside the database with information about the storaged file even when the attachment is deleted before the item and the item nor the file exist anymore.
How can the maintainer reproduce the issue?
Create an item and add a photo.
Look at the last file created in data/group-id-code-here/documents, it will be there.
Delete the item, the photo will still be in the storage path pointed above.
Create another item and add a photo.
Look at the last file created in data/group-id-code-here/documents, it will be there.
Access this last created item, edit it, and delete the photo.
The photo should be deleted from the storage path pointed above.
Now delete the item.
Deployment
Other
OS Architechture
x86_64 (AMD, Intel)
Deployment Details
I'm using the latest binary release to Linux 64 bits, homebox_Linux_x86_64.tar.gz in a Debian 12 system.
The text was updated successfully, but these errors were encountered:
First Check
Homebox Version
0.16.0
What is the issue you are experiencing?
When I create an Item and add a photo or any other attachment, and later delete it, the attachments are not deleted, it is just abandoned inside .data/group-id-code-here/documents. Unless I edit the item and delete the attachments one by one, then it deleted correctly from storage. There should be a lot of attachments that are no longer used lying around in my storage.
I was wondering too why the system maintains a record inside the documents table inside the database with information about the storaged file even when the attachment is deleted before the item and the item nor the file exist anymore.
How can the maintainer reproduce the issue?
Create an item and add a photo.
Look at the last file created in data/group-id-code-here/documents, it will be there.
Delete the item, the photo will still be in the storage path pointed above.
Create another item and add a photo.
Look at the last file created in data/group-id-code-here/documents, it will be there.
Access this last created item, edit it, and delete the photo.
The photo should be deleted from the storage path pointed above.
Now delete the item.
Deployment
Other
OS Architechture
x86_64 (AMD, Intel)
Deployment Details
I'm using the latest binary release to Linux 64 bits, homebox_Linux_x86_64.tar.gz in a Debian 12 system.
The text was updated successfully, but these errors were encountered: