mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[Issue]: Possible clue/root cause to "Can't add films with multiple versions to collections" #5996
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @brunoherrera on GitHub (Jun 12, 2024).
Please describe your bug
Basically this: #11736
Possible lead:
I think the issue is related to nfo files, because the movie with multiple versions gets a 'movie.nfo' and only one 'mofieFileNameHere.nfo', when that movie is added to a collection, the [boxset] collection.xml references a
<Path>to a movie version that doesn't have a 'mofieFileNameHere.nfo' generated, as soon as you edit collection.xml and change the path of the problematic movie to the one that actually has a mofieFileNameHere.nfo generated, and refresh metadata for the collection it shows up, though it will not show up with all the versions of the movies and will only display the version that has the mofieFileNameHere.nfo generatedReproduction Steps
Jellyfin Version
10.9.0
if other:
No response
Environment
Jellyfin logs
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@Shadowghost commented on GitHub (Jun 12, 2024):
Are your NFOs generated by Jellyfin? If yes, we should only use
movie.nfoas fallback.@brunoherrera commented on GitHub (Jun 12, 2024):
yes, I'm letting Jellyfin generate them
@Shadowghost commented on GitHub (Jun 12, 2024):
The behaviour was changed in #10339 and quite intensively tested. I'm currently investigating why this doesn't break movie metadata but instead breaks collections.
@Shadowghost commented on GitHub (Jun 12, 2024):
@brunoherrera can you please post the exact file layout of a movie where it is failing? I was unable to reproduce it so far.
@brunoherrera commented on GitHub (Jun 12, 2024):
G:\JELLYFIN\MOVIES\X-Men - Days of Future Past (2014) (1080p BluRay x265 HEVC 10bit AAC 7.1 Tigole)backdrop.jpgfolder.jpglandscape.jpglogo.pngmovie.nfoX-Men - Days of Future Past (2014) (1080p BluRay x265 HEVC 10bit AAC 7.1 Tigole) - The Rogue Cut.mkvX-Men - Days of Future Past (2014) (1080p BluRay x265 HEVC 10bit AAC 7.1 Tigole) - The Rogue Cut.nfoX-Men - Days of Future Past (2014) (1080p BluRay x265 HEVC 10bit AAC 7.1 Tigole) - Theatrical Version.mkv@theguymadmax commented on GitHub (Jun 12, 2024):
I had the same issue with the 10.8 releases. I renamed/removed a movie that had multiple versions, which was already in the library. Jellyfin did not like that! #4601
No matter what I did, I couldn't get the movie back into the collection. Jellyfin kept trying to add it back into the collection, spamming the xml file.
Ultimately I looked in the library database and saw the old filenames were still there #12070. Removing the old entries allowed me to finally add the movie back into the collection.
@ashanrath commented on GitHub (Jun 27, 2024):
@theguymadmax can you clarify what old entries you removed? I tried removing all of the .nfo files in one of my root directories and doing a full scan, set to replace all metadata. The same issue occurred, though randomly on different entries then before. E.g. my initial problem was with "A New Hope" - wiping all the .nfo and rescanning fixed "A New Hope" but now I can't get "Return of the Jedi" in the collection. I suspect that it may be related to which version is scanned first, depending on version file names.
Should I instead be only wiping the .nfo and leaving the .nfo intact before rescanning?
@jellyfin-bot commented on GitHub (Oct 25, 2024):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@ashanrath commented on GitHub (Oct 25, 2024):
Still an issue.
@SciKoLogic commented on GitHub (Nov 5, 2024):
I think I suffer from the same issue although I do not have multiple versions of the movie.
I suspect a renaming of the file in question likely happened way back and now when I've tried to add it to a collection it simply does not want to.
In the collection.xml I can see it get added when I click "add to collection" and now, every time I scan my library I can see it get added again (in the collection.xml, not replacing the old entry but rather as a new one, a duplicate).
If I'm to guess a repro it would go something like this:
If the repro is successful also notice how every time you scan your library the test movie gets another entry in your created collection's collection.xml.
@thamow commented on GitHub (Nov 30, 2024):
I seem to have the same issue. HOWEVER when I tried the workaround described by the first post from @brunoherrera, the issue persists and the movies are not added. Additionally, one of the three movies I tried to add to the same collection does actually show up, despite it having multiple versions and the .nfo situation being the same as well!
Captain America - Civil War (2016) - 2160p.mkv shows up, the other two don't:
Captain America - Civil War (2016)
Captain America - The First Avenger (2011)
Captain America - The Winter Soldier (2014)
@thamow commented on GitHub (Dec 1, 2024):
I have found a workaround - which I am not very happy with. If you add [] around the version (so e.g. 'Captain America - The Winter Soldier (2014) - [1080p].mkv' and so on), it works flawlessly. I am not happy with this, because it means that in the frontend the version contains those square brackets as well (so it shows up as [1080p] in the drop down)...
(Trying this was not my idea but I cannot credit whomever did come up with this, since I can't find the original post anymore. Maybe it was them).
@theguymadmax commented on GitHub (Feb 11, 2025):
Closing as a duplicate of #11736. Other thread as more detailed info as to the cause of the issue.