Replies: 1 comment
-
|
Just now realizing that "Empty Trash" is what should be used in as situation like this. I'll leave the issue open however, incase a dev feels this is an actual issue, or if there is another method of removal recommended. Otherwise, please close when necessary. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Steps to reproduce
Expected behavior
The selected entry should be removed from Komga, even if the path or file doesn't exist.
Actual behavior
Entry for series or book(s) remain unchanged, still listed as "Unavailable"
Logs
Komga version
v1.24.1-master
Operating system
Podman / Linux
Installation method
Docker
Other details
If a deletion request is made, the entry should be removed even if it does exist BUT Komga does not have Read-Write permission (ex. running under Docker with :ro on the mount path).
Otherwise, Komga should be auto-removing entries that are unavailable, as it doesn't make sense why they should be kept around...
Acknowledgements
Beta Was this translation helpful? Give feedback.
All reactions