It seems like the API is returning empty results for some movies when it should return actual results.
Here's an example:
This works: https://api.themoviedb.org/3/movie/550/images?api_key=###.
This doesn't: https://api.themoviedb.org/3/movie/63492/images?api_key=###
The second movie, What's Your Number, has lots of images that should be displayed when using that call, but it doesn't work. Any help?
I've read this following topic, but I'm not making any calls with a language filter: http://www.themoviedb.org/talk/508ecd2f19c295550b0000ba. Curiously, though, it does work when adding a language parameter. Shouldn't it return all images when not specifying the language?
Can't find a movie or TV show? Login to create it.
Vil du vurdere eller legge til dette elementet i en liste?
Ikke et medlem?
Svar av Travis Bell
den 6 November 2012 kl. 8:27 PM
Seemed to be just a random cached item that was borked somehow. 63492 seems to be working ok now that I cleared it.
I haven't seen this before today, are there other movies doing it?
Svar av Michell Bak
den 6 November 2012 kl. 8:35 PM
Cool, thanks. Seems to be working now.
It's been happening with various movies during the past few weeks at least. It's rarely the same movie, but does seem to happen to several movies at a time. I'm testing my app with 56 different movies, and I've been experiencing problems with several movies at times.
Svar av emmaqian
den 11 November 2012 kl. 9:14 AM
I hit the same issue. I queried 'http://api.themoviedb.org/3/movie/550/images' and got empty result. It worked for 551.
BTW, as Michell said, it can be worked-around by specifying the 'language' parameter. However, how to select those with 'null' language?
Svar av Michell Bak
den 11 November 2012 kl. 10:43 AM
My work-around to the issue is to query the database without specifying the language parameter, and if that doesn't return any results, my application will try with the language parameter set to English. It's not 100% perfect, but it'll work in most cases for the most well-known movies.
@emmaqian If you don't set the language parameter, it'll also include the null ones. I think that's the only way.
@Travis Bell I think there might be problems with the caching of results. It's happening a lot lately.
Svar av MikeyCarter
den 15 November 2012 kl. 4:48 PM
curl "http://api.themoviedb.org/3/movie/10946/images?api_key=***" {"id":10946,"backdrops":[],"posters":[]}
curl "http://api.themoviedb.org/3/movie/10946/images?api_key=***&language=de" {"id":10946,"backdrops":[],"posters":[{"file_path":"/fIuLDQ8gEJtSEuNHBsQO0Bm9fA1.jpg","width":1000,"height":1500,"iso_639_1":"de","aspect_ratio":0.67,"vote_average":0.0,"vote_count":0}]}
So how do I get to the "no language" images? specifying no language isn't working for me.
Svar av Travis Bell
den 15 November 2012 kl. 5:18 PM
By not specifying a language param.
This call has all the images for me…
Svar av MikeyCarter
den 15 November 2012 kl. 5:25 PM
It does now. And I think that's because I move one of the images to be "english"
Svar av hosam
den 22 November 2012 kl. 8:35 AM
If I had to guess.
That bug seems to only affect movies with all the backdrops or posters as "No Language"
Svar av hosam
den 22 November 2012 kl. 9:11 AM
Okay I don't think it is because "UP" has only no language backdrops and I can query that. I guess something is wrong with caching
Svar av hosam
den 28 November 2012 kl. 8:28 AM
Seems like the backdrops are totally broken when using the append_to_response to a movie details
https://api.themoviedb.org/3/movie/1366?api_key=####&language=en&append_to_response=images
That returns posters and empty backdrops. Same goes for every movie I tried
Svar av Michell Bak
den 28 November 2012 kl. 8:36 AM
It's not broken, it just appends the language parameter to the image query as well. The image caching may very well be a bit buggy, though.
Svar av hosam
den 28 November 2012 kl. 8:39 AM
ah just noticed, thanks. That is bit problematic though because backdrops are normally without a language. I would suppose a call to english returns english backdrops and no language as well. I open a new discussion for that.
Svar av Travis Bell
den 28 November 2012 kl. 10:30 AM
Maybe but I really hate having a one off workaround that doesn't follow the standard of the rest of the API.
What could make more sense is that the image calls support being queried by more than one language. Then it's very clear what is happening. Something like this:
Then there's no magic (which I hate) and it's easy to fallback on language data within a single request.
Regarding the core bug being discussed here though, I'll be looking at it this week sometime. This week is all about the API.
Svar av hosam
den 28 November 2012 kl. 11:13 AM
That would work as well. Good luck dude :) and thanks a lot for all your epic efforts on the API
Svar av Michell Bak
den 28 November 2012 kl. 11:30 AM
That would be splendid! Please keep us updated, Travis :-)