Hi anderbytes,

Thanks for the report. I've created a new ticket for this here. It's a weird one, no doubt.

Cheers.

Don't know if something has been done.... but now the original query above works normaly.

I'd like to complement this thread with another strange issue that I just found today concerning collections:

http://api.themoviedb.org/3/collection/121938?api_key=###API_KEY_HERE####&append_to_response=images&language=pt-BR&include_image_language=pt-br,null,en --> field "Overview" returns "" (correct, empty string)

http://api.themoviedb.org/3/collection/119?api_key=###API_KEY_HERE####&append_to_response=images&language=pt-BR&include_image_language=pt-br,null,en --> field "Overview" returns NULL (incorrect... can cause errors in clients)

Can you please investigate why the 2nd one brings nulls ?? Empty is expected. From TheMovieDB website I can't tell what is causing this, they seem both correctly filled with data.

Thanks!

Ohhhhhh, so your first one was probably just the cache. I didn't even look to see if you had updated the data on the 27th (and you did). The API will cache data for 6-8 hours so after making changes on the website and the item is already in cache, you'll have to wait for the item to be purged.

Re: null overviews, all of the movie and collection responses will return null if the translation doesn't exist... this is something I can look at updating later. null is a perfectly valid JSON data type like a string or an integer. It shouldn't cause any problems.

Strange... I recall translating those collections yesterday.... and now they don't seem to have in my language. Well... I'll just translate them again, and check back tomorrow morning.

About the "empty vs null". The thing is.... the query returned lot of pt-BR data (title, parts, that existed yesterday... I swear) , but NULL in overview.

Maybe some type of row corruption in DB? Next time I'll have the care of copying the result JSON

About the "empty vs null". The thing is.... the query returned lot of pt-BR data (title, parts, that existed yesterday... I swear) , but NULL in overview.

Different params will force a new item into the cache so depending when an original request was made and then when the data was edited AND if you are playing around with different params you will get different versions of the assets. So the long and short of it is you can't really dig too much into anything until you know the data has been refreshed which is always just best to wait the ~6 hours after an edit.

You can also check the X-Memc-Expires header to see when exactly the cached item will expire in seconds.

Thanks for the tip. Will pay attention to that next time before posting. :-)