The Movie Database 支持
支持 → API 支持
Problem with images
Michell BakSTAFFMOD 发布于 2012 年 11 月 06 日 8:00下午
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?
Travis Bell 的回复
于 2012 年 11 月 06 日 8:27下午
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?
Michell Bak 的回复
于 2012 年 11 月 06 日 8:35下午
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.
emmaqian 的回复
于 2012 年 11 月 11 日 9:14上午
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?
Michell Bak 的回复
于 2012 年 11 月 11 日 10:43上午
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.
MikeyCarter 的回复
于 2012 年 11 月 15 日 4:48下午
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.
Travis Bell 的回复
于 2012 年 11 月 15 日 5:18下午
By not specifying a language param.
This call has all the images for me…
MikeyCarter 的回复
于 2012 年 11 月 15 日 5:25下午
It does now. And I think that's because I move one of the images to be "english"
hosam 的回复
于 2012 年 11 月 22 日 8:35上午
If I had to guess.
That bug seems to only affect movies with all the backdrops or posters as "No Language"
hosam 的回复
于 2012 年 11 月 22 日 9:11上午
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
hosam 的回复
于 2012 年 11 月 28 日 8:28上午
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
Michell Bak 的回复
于 2012 年 11 月 28 日 8:36上午
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.
hosam 的回复
于 2012 年 11 月 28 日 8:39上午
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.
Travis Bell 的回复
于 2012 年 11 月 28 日 10:30上午
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.
hosam 的回复
于 2012 年 11 月 28 日 11:13上午
That would work as well. Good luck dude :) and thanks a lot for all your epic efforts on the API
Michell Bak 的回复
于 2012 年 11 月 28 日 11:30上午
That would be splendid! Please keep us updated, Travis :-)