
GET /series/{id} returning title with "en" title instead of the specified lang
Forum rules
This forum is now read-only. Support for TheTVDB.com is now available at https://support.thetvdb.com/
This forum is now read-only. Support for TheTVDB.com is now available at https://support.thetvdb.com/
The issue I described still exists.
In the latest "Known Issues Log & Status" topic this thread is marked as fixed:
In the latest "Known Issues Log & Status" topic this thread is marked as fixed:
But the issue still exists. Do I have to open a seperate thread or is this already in your ticket system? I guess these are two different bugs.GET /series/{id} returning title with "en" title instead of the specified lang — Released 1/8 | related forum thread
Issue still persists. All Norwegian shows (language ID: 9) returns English title instead of Norwegian:
Response is in English, instead of Norwegian:
Code: Select all
curl -X GET --header 'Accept: application/json' --header 'Accept-Language: no' --header 'Authorization: Bearer [TOKEN]' 'https://api.thetvdb.com/series/300820'
Code: Select all
{
"data": {
"id": 300820,
"seriesId": "",
"seriesName": "Adam searches Eva",
"aliases": [],
"season": "1",
"poster": "posters/300820-1.jpg",
"banner": "",
"fanart": "fanart/original/300820-1.jpg",
"status": "Ended",
"firstAired": "2015-09-17",
"network": "TVNorge",
"networkId": "367",
"runtime": "1",
"language": "en",
"genre": [
"Reality"
],
"overview": "Norwegian realityshow",
"lastUpdated": 1577492822,
"airsDayOfWeek": "Thursday",
"airsTime": "9:30 PM",
"rating": null,
"imdbId": "",
"zap2itId": "",
"added": "2015-09-17 18:05:43",
"addedBy": 46732,
"siteRating": 0,
"siteRatingCount": 0,
"slug": "300820"
}
}
-
- Posts: 4
- Joined: Fri Apr 17, 2020 10:14 pm
API still returns English info when requesting specifically Norwegian, like the post above.
This seems limited to Norwegian, because other nordic languages return correct.
Can anyone take a look at this?
This seems limited to Norwegian, because other nordic languages return correct.
Can anyone take a look at this?
-
- Posts: 4
- Joined: Fri Apr 17, 2020 10:14 pm
Okay, I have researched this a bit further, and it seems that you have mixed up the different Norwegian language codes internally in the API.
The API returns the following as valid info,
But the correct language code for "Norsk Bokmål" is 'nb', not 'no', and when I use the language code 'nb' in the API requests, I get the correct Norwegian info in response.
You seem to have half-way changed from Norsk 'no' to Norsk Bokmål 'nb', when upgrading the API.
The API returns the following as valid info,
Code: Select all
"id": 9,
"abbreviation": "no",
"name": "Norsk bokmål",
"englishName": "Norwegian"
You seem to have half-way changed from Norsk 'no' to Norsk Bokmål 'nb', when upgrading the API.
-
- Site Admin
- Posts: 1509
- Joined: Tue Feb 26, 2019 12:01 pm
Hi,Gyldendahl wrote: ↑Mon Apr 27, 2020 4:15 pmOkay, I have researched this a bit further, and it seems that you have mixed up the different Norwegian language codes internally in the API.
The API returns the following as valid info,But the correct language code for "Norsk Bokmål" is 'nb', not 'no', and when I use the language code 'nb' in the API requests, I get the correct Norwegian info in response.Code: Select all
"id": 9, "abbreviation": "no", "name": "Norsk bokmål", "englishName": "Norwegian"
You seem to have half-way changed from Norsk 'no' to Norsk Bokmål 'nb', when upgrading the API.
Yes, you are technically right. In the past, we actually stored both no and nb previously and a user pointed out that other users were mixing stuff up between the choices. The decision was made to combine both no and nb into a single language called Norwegian (no) and put all the records together into that. I've run it past our devs and I think we will stick to this decision. Apologies for the confusion.
-
- Posts: 4
- Joined: Fri Apr 17, 2020 10:14 pm
Hi,ChristyEzzell wrote: ↑Tue Apr 28, 2020 4:16 pmHi,
Yes, you are technically right. In the past, we actually stored both no and nb previously and a user pointed out that other users were mixing stuff up between the choices. The decision was made to combine both no and nb into a single language called Norwegian (no) and put all the records together into that. I've run it past our devs and I think we will stick to this decision. Apologies for the confusion.
Thank you for responding to this.
This is all well and good, but is it not a bug that I do not get the correct Norwegian info when using 'no', but instead get the correct info when using 'nb'?
Especially since the API returns 'no' as the valid abbreviation.
Do I start using 'nb' instead of 'no'?
-
- Site Admin
- Posts: 1509
- Joined: Tue Feb 26, 2019 12:01 pm
You should use "no."Gyldendahl wrote: ↑Wed Apr 29, 2020 1:58 amHi,ChristyEzzell wrote: ↑Tue Apr 28, 2020 4:16 pmHi,
Yes, you are technically right. In the past, we actually stored both no and nb previously and a user pointed out that other users were mixing stuff up between the choices. The decision was made to combine both no and nb into a single language called Norwegian (no) and put all the records together into that. I've run it past our devs and I think we will stick to this decision. Apologies for the confusion.
Thank you for responding to this.
This is all well and good, but is it not a bug that I do not get the correct Norwegian info when using 'no', but instead get the correct info when using 'nb'?
Especially since the API returns 'no' as the valid abbreviation.
Do I start using 'nb' instead of 'no'?
-
- Posts: 4
- Joined: Fri Apr 17, 2020 10:14 pm
Then it is a bug that is known and will be fixed, that it returns english info when I use 'no'?
-
- Site Admin
- Posts: 1509
- Joined: Tue Feb 26, 2019 12:01 pm
I'l ticket this. I see translations in NO against the series and the first three episodes.