Hello! I´d like to report an issue with the actual image fetching API.
When a query gives any kind of country-Region language as parameter (Ex: pt-BR , en-GB, etc...), then the API doesn't return anything... because images are registered in DB only with the first characters of the COUNTRY (pt , en, es, ru, etc...).
I'd like to ask the devs to make a modification. When a query with 2-part language comes, please discard the trace and 2nd part, and use only the 2 first digits to execute the query and bring the results.
Can't find a movie or TV show? Login to create it.
Want to rate or add this item to a list?
Not a member?
Reply by Travis Bell
on May 31, 2016 at 1:56 PM
Hi anderbytes,
Images haven't been migrated yet. At this time, I don't have an ETA as to when I'll get to them. Images will be a decently large undertaking and I'm not sure I'll be able to efficiently add support for the extra queries without re-writing the image service. All I can say is that I should be able to get to it this year, but beyond that I can't say.
Cheers.
Reply by anderbytes
on May 31, 2016 at 2:13 PM
Thanks for the effort.
Besides creating different country-Region options, I understand that it will be difficult to know what to do with the existing images, that are probably mixed up between countries for the same language.
Reply by anderbytes
on July 1, 2016 at 9:45 PM
Travis, while you don't create the new structure that supports 5-digit language code instead of 2-digit, can you PLEASE do some workaround?
Like this: when a 5-digit query comes... serve it's metadata as usual (because the metadata DB has 5-digit), but when looking for images matches, consider only the first 2 digits of the 5-digit code inputted, then it will return correct language images, instead of excluding them.
Reply by Travis Bell
on July 2, 2016 at 10:49 AM
Hi anderbytes,
I'm not sure if I understand the issue you're describing. The system as it stands today will only take the first 2 characters of a language key for images (that's the issue, it ignores the country). But the language query itself is still working.
Both return http://image.tmdb.org/t/p/original/rxmF5Eb4J3ev3I10swoCqhShVuq.jpg as the poster, for example. The part of this that isn't hooked up is the country query, so in essence, this is just working the same way that a vanilla
pt
query worked before since that's all that is stored in our image database.Reply by anderbytes
on July 2, 2016 at 12:01 PM
I now understand why the confusion happened.
The app that I use and fetches images uses a specific query url to fetch several images (specific languages, english as fallback, etc...), and goes to https://api.themoviedb.org/3/movie/296100?api_key=#####&append_to_response=casts,releases,images,keywords,trailers&language=pt-BR&include_image_language=pt-br,null,en
so the variable that TMDB ignores 5-digit is "include_image_language", not "language".
Reply by anderbytes
on July 2, 2016 at 12:19 PM
I'll tro to ask the other dev to use poster_path , but please considere that include_image_language still ignores 5-digit inputted.
It could use the first 2 digit there
Reply by anderbytes
on July 12, 2016 at 5:43 AM
The other app's dev has skirted the client-side of the issue by changing the query specifically to TMDB and trimming to 2-digit. So... I have no rush anymore, but the issue still exists, ok? :-/
So... about the "include_image_language" parameter... can you confirm it doesn't support 5-digit language? Thanks
Reply by Travis Bell
on July 12, 2016 at 9:39 AM
That's great, the
include_image_language
does not support thept-BR
notation yet, and indeed I think I'm just splitting the values and passing them to the DB so by specifying the full 5 chars, it's not going to find anything. Obviously when images get properly updated, this will start working. For now, you'll have to pass justpt
in.Reply by anderbytes
on September 12, 2016 at 4:45 PM
Any estimate on create 5-digit image language databases? To difference images from "pt" to "pt-PT" and "pt-BR" ?
Reply by Travis Bell
on September 12, 2016 at 4:50 PM
I do not have an estimate at this time. Like I mentioned above, it's a pretty massive job and one that I don't think I have time for in the immediate near future. It's on deck but so are like 100 other things ;)
Reply by anderbytes
on September 12, 2016 at 8:07 PM
Hehe no prob. Just asking.
I'll be coming back in this post by 2017. See ya
Reply by anderbytes
on January 9, 2017 at 4:41 AM
Hello again Travis.
Is that feature in the next Top 50, maybe? :-)
Reply by Travis Bell
on January 9, 2017 at 11:22 AM
Haha, yes, probably top 50 but still not in my immediate plans. Based on what I have laid out at the moment, I'd say another few months.
Reply by anderbytes
on June 5, 2017 at 3:00 PM
Pretty please? :-)
Reply by Travis Bell
on June 6, 2017 at 11:45 AM
Hopefully I'll find time this year but there are many items that are higher priority. I can't make any estimate as to when I will get to this one.