[Issue]: Possible clue/root cause to "Can't add films with multiple versions to collections"

[brunoherrera]

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 generated

Reproduction Steps

1. Add a film with multiple versions to a film library
2. Add that film to a collection
3. Check if it appears in the collection

Jellyfin Version

10.9.0

if other:

No response

Environment

- OS: Windows 10
- Linux Kernel: /
- Virtualization: /
- Clients: Jellyfin Web
- Browser: Chrome
- FFmpeg Version: 2023-09-07-git-9c9f48e7f2-full_build-www.gyan.dev
- Playback Method: /
- Hardware Acceleration: yes
- GPU Model: Evga FTW3 Black RTX 3090 TI
- Plugins: AudioDB, MusicBrainz, OMDb, Open Subtitles, Reports, Studio Images, TMDb, TMDb Trailers, Webhook, YoutubeMetadata
- Reverse Proxy: /
- Base URL: /
- Networking: /
- Storage: /

Jellyfin logs

nothing relevant

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[Shadowghost]

Are your NFOs generated by Jellyfin? If yes, we should only use movie.nfo as fallback.

[brunoherrera]

Are your NFOs generated by Jellyfin? If yes, we should only use movie.nfo as fallback.

yes, I'm letting Jellyfin generate them

[Shadowghost]

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]

@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]

@brunoherrera can you please post the exact file layout of a movie where it is failing? I was unable to reproduce it so far.

G:\JELLYFIN\MOVIES\X-Men - Days of Future Past (2014) (1080p BluRay x265 HEVC 10bit AAC 7.1 Tigole)
backdrop.jpg
folder.jpg
landscape.jpg
logo.png
movie.nfo
X-Men - Days of Future Past (2014) (1080p BluRay x265 HEVC 10bit AAC 7.1 Tigole) - The Rogue Cut.mkv
X-Men - Days of Future Past (2014) (1080p BluRay x265 HEVC 10bit AAC 7.1 Tigole) - The Rogue Cut.nfo
X-Men - Days of Future Past (2014) (1080p BluRay x265 HEVC 10bit AAC 7.1 Tigole) - Theatrical Version.mkv

[theguymadmax]

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]

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.

@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]

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]

Still an issue.

[blomgrenskold]

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:

0. (Optional) Add a "movie.nfo" file in the same folder as the movie to be tested. Make sure it does not get edited by Jellyfin before continuing.
1. Go to your library containing the movie to test and choose "Manage Library" and tick "Automatically add to collection".
2. Go to Libaries -> Display and tick "Group movies into collections".
3. Add an existing movie to a collection and then add your test movie to that same collection.
4. Confirm it's added in "Jellyfin/data/collections/YOURCOLLECTIONNAME [boxset]/colllection.xml"
5. Rename the existing movie's filename (if that doesn't do it perhaps replacing the file without removing it's .nfo file will do).
6. Scan your library
7. Hopefully notice how the movie no longer shows in the collection you added it to.

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.