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
Describe the bug
I just ran into this by accident. It seems that the directory I'm trying to save into has a permissions issue (which I did not realise before), and so ME doesn't have write-access. When saving the movie, it reports a successful save, but as you can imagine, it didn't actually save anything.
To Reproduce
Steps to reproduce the behavior:
Have a directory with missing write permissions
Scrape directory for a movie and save
Check the upper right corner and/or console logs
Expected behavior
ME should notify the user about the failed save, if possible with an appropriate error message (as seen in the console log warning).
Screenshots
MediaElch Version:
2.10.6 (stable)
Operating System:
Linux (distribution: Fedora 39)
Additional context
Movie is on a NAS, mounted on an NFS share. Seems I messed up my permissions somewhere.
The text was updated successfully, but these errors were encountered:
Thanks for reporting! Yes, that's a bug. In fact, the log entry is my first approach to log something. A few versions ago, nothing was printed at all. However, I totally forgot about that. It should definitely be shown to the user!
Describe the bug
I just ran into this by accident. It seems that the directory I'm trying to save into has a permissions issue (which I did not realise before), and so ME doesn't have write-access. When saving the movie, it reports a successful save, but as you can imagine, it didn't actually save anything.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
ME should notify the user about the failed save, if possible with an appropriate error message (as seen in the console log warning).
Screenshots
MediaElch Version:
Operating System:
Additional context
Movie is on a NAS, mounted on an NFS share. Seems I messed up my permissions somewhere.
The text was updated successfully, but these errors were encountered: