-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Allow using alternate order #49
Comments
Their API v3 doesn't allow it. Maybe in v4... |
API v4 endpoint {
"data": [
{
"aliases": [
{
"language": "string",
"name": "string"
}
],
"id": 0,
"isOfficial": true,
"name": "string",
"nameTranslations": [
"string"
],
"overview": "string",
"overviewTranslations": [
"string"
],
"url": "string"
}
],
"status": "string"
} I guess it may be for that? Not sure. |
Or possibly the |
Yes, this will come with API V4. |
Is there any update on this? I have a series that I would like to use the "Saga" order, which according to TVDB is accessible via Alternate Order |
Any updates? |
Adding more info on this issue using 'The Office' as example, hope this can help! TVDB Ids Steps to reproduce
Issue Additional Any ideas on how to solve this on Jellyfin? |
While I think this is implementable, it will require some arbitrary mappings that might not be intuitive for the end-user since out of all the orders provided by the Tvdb api, Jellyfin only supports aired, absolute and dvd. The rest will have to be arbitrarily mapped, like Jellyfin's "Story Arc" option could be mapped to Tvdb's "alternate". @crobibero thoughts? |
I think we could expand Jellyfin's display order? At the same time it would be nice to have it as an enum instead of a free string |
I believe the plugin doesn't allow using alternate episode orders, which would be great
And example of a series with alternative order is La casa de papel.
The “official” order is:
Though one may want to use the Netflix order:
I presume there could be some way to change the order of a single show, and keep the current behavior as default.
The text was updated successfully, but these errors were encountered: