Fix 500 error on items related to tmdb id handling - #124
Merged
dannyvfilms merged 2 commits intoApr 1, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I was experiencing an issue with England by Tom Scott when attempting to log view history. Not sure if others are experiencing the same with anything else.
I did have to manually alter my sqlite db to remove references to the incorrect TMDB ID, but seems to all be functioning now.
I am also not a developer by trade and was assisted by Claude throughout.
tmdb.py:
process_tv now accepts and threads through the correct media_id rather than always using the raw response["id"], fixing season card links
_build_specials_season_from_tvdb now catches ProviderAPIError so a bad/missing TVDB ID doesn't crash the page
views.py:
The specials enrichment call in media_details is now wrapped in a try/except for ProviderAPIError for the same reason