When the DB stored a path the resolver couldn't map to a local file (common with Navidrome virtual paths or Docker path mismatches), file deletion was silently skipped — the DB record was removed but the file stayed on disk with no indication to the user. Now logs the resolution failure with the stored path, returns a file_error in the API response, and the frontend shows a warning toast explaining the file wasn't deleted plus a second toast with the specific reason (e.g. Navidrome 'Report Real Path' instructions). |
||
|---|---|---|
| .. | ||
| static | ||
| index.html | ||