The Movie Database サポート

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?

22 replies (on page 1 of 2)

Jump to last post

次のページ最後のページ

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?

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.

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?

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.

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.

So how do I get to the "no language" images?

By not specifying a language param.

This call has all the images for me…

http://api.themoviedb.org/3/movie/10946/images?api_key=###

It does now. And I think that's because I move one of the images to be "english"

If I had to guess.

That bug seems to only affect movies with all the backdrops or posters as "No Language"

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

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

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.

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.

I would suppose a call to english returns english backdrops and no language as well.

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:

https://api.themoviedb.org/3/movie/550/images?api_key=###&language=en,null

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.

That would work as well. Good luck dude :) and thanks a lot for all your epic efforts on the API

That would be splendid! Please keep us updated, Travis :-)

映画やテレビ番組が見つかりませんか?ログインして作成してください。

全般

s 検索バーに移動する
p プロファイルメニューを開く
esc 開いているウィンドウを閉じる
? キーボードショートカットウィンドウを開く

メディアのページ

b 戻る(または該当する場合は親に)
e 編集ページに行く

テレビ番組のシーズンのページ

(右矢印)次のシーズンに行く
(左矢印)前のシーズンに戻る

テレビ番組のエピソードのページ

(右矢印)次のエピソードに進む
(左矢印)前のエピソードに戻る

全ての画像のページ

a 画像追加ウィンドウを開く

全ての編集ページ

t 翻訳選択を開く
ctrl+ s フォームを送信する

ディスカッションのページ

n 新しいディスカッションを作成する
w 監視ステータスを切り替える
p 公開/非公開を切り替える
c 閉じる/開くを切り替える
a アクティビティを開く
r ディスカッションに返信
l 最後の返事に行く
ctrl+ enter メッセージを送信する
(右矢印)次のページ
(左矢印)前のページ

設定

このアイテムを評価したり、リストに追加したりしたいですか?

ログイン

メンバーではありませんか?

登録してコミュニティに参加