-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Issue]: NFO watched status not imported for movies or episodes #8415
Comments
Meant to put #1640 |
Could you maybe provide us one of your nfo files and your nfo config file? You should find the latter at in you configuration folder at |
Yes! I will work on getting both of those this week and post in here. Thanks! |
@matthewpritchett, Did you find the solution to your issue? |
No solution besides using a third party tool to sync watch statuses. I just forgot to post my debug info here. Hopefully sometime soon I’ll get time to. |
I have this same issue too. The watched status (and lastplayed dates) from my nfo files (created by Emby) are not coming across to Jellyfin 10.8.8 |
Well, as you can see, I ended up looking into it myself, and I think I found the source of the issue. |
Please describe your bug
Same issue as the previously resolved #1640
I am working on migrating my server from an Ubuntu install to a Truenas Scale (using Truecharts) installation and since I already have all metadata and watched status saved in NFO files I tested the import process and it seems like it isn’t reading the watched tags in the NFO file. I disabled all other metadata providers and had disabled saving NFO before importing as well as setting the user for watched status. I import and the majority of data from the NFO is imported correctly but watched is always shown as false on the webui. Curious if there’s anything specific I need to set for it to work or if it might be a bug introduced since the previous issue was fixed. Thanks!
Jellyfin Version
10.8.0
if other:
No response
Environment
Jellyfin logs
No response
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: