Skip to content
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

Jellyfin v10.9.1 isn't respecting the metadata lock for Season names in Show libraries causing custom season names to be lost. #11656

Open
maru801 opened this issue May 14, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@maru801
Copy link

maru801 commented May 14, 2024

Describe The Bug
For a Show library that contains series with seasons, you're allowed to manually overwrite the title names for each season. You can then lock the metadata for the name so that its title will not change upon a future scan. This is how it worked before v10.9.0.

However, since upgrading to v10.9.0 (and v10.9.1), Jellyfin doesn't respect the metadata lock for the season name/title. With v10.9, a rescan of any season will prompt the server to change the name of any season to be "Season x" where x is the season number in the metadata.

Steps To Reproduce

  1. Go to a show that has at least one season.
  2. Edit the season's metadata and change its title to be anything. After changing the name, make sure to scroll to the bottom of the metadata edit popup to lock the name. Either uncheck the "Name" box, or select the "Lock this item to prevent future changes" box.
  3. Reload the client, then navigate to the same show to see your change to the season's name.
  4. Refresh the metadata for the whole show (to capture the season(s) as well), and select the "Scan for new and updated files" option. You can also go to the dashboard and use the "Scan All Libraries" button to get this same result.
  5. Wait a short while to let the scan do its work.
  6. Reload the client again, then navigate to the same show. You'll notice the client changed the custom name you gave the season back to "Season x" despite you locking it.

Expected Behavior
Jellyfin should respect the metadata lock and not change any season's name if you set a custom name for the season.

System (please complete the following information):

  • Platform: Linux
  • Browser: Any
  • Jellyfin Version: v10.9.1

Additional Context
The names seem to be pulled from the .nfo files I have saved next to the media files. If the .nfo has a season number stored with it, doing the above will show the error as I describe. I found that if I remove the season number from the season's .nfo files, this bug doesn't happen.

@maru801 maru801 added the bug Something isn't working label May 14, 2024
@thornbill thornbill transferred this issue from jellyfin/jellyfin-web May 15, 2024
@jellyfin-bot
Copy link
Contributor

Hi, it seems like your issue report has the following item(s) that need to be addressed:

  • This bug report was not filed using the issue template.

This is an automated message, currently under testing. Please file an issue here if you encounter any problems.

@gnattu
Copy link
Member

gnattu commented May 15, 2024

Should be fixed by #11647

@maru801
Copy link
Author

maru801 commented May 18, 2024

This issue was fixed with the server version v10.9.2.

@maru801 maru801 closed this as completed May 18, 2024
Issue Triage for Main Repo automation moved this from Needs triage to Closed/Done May 18, 2024
@maru801
Copy link
Author

maru801 commented May 19, 2024

Reopening this as I found out that v10.9.2 only fixed the season names from being changed when using the dashboard's "Scan All Libraries" or the "Scan for new and updated files" option for all else. Still, If you scan a season with either the "Search for missing metadata" or "Replace all metadata" options, it will still have its title name changed despite being locked.

And what's more, some seasons are now getting their season name changed to that of another season of another series when scanned. I don't understand what is going on here.

@maru801 maru801 reopened this May 19, 2024
Issue Triage for Main Repo automation moved this from Closed/Done to Needs triage May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: No status
Development

No branches or pull requests

3 participants