When I query the latest movie using /3/movie/latest, and then try to get the basic info using the TMDB id returned: /3/movie/{the TMDB id that was returned} I get back: {u'status_code': 6, u'status_message': u'Invalid id - The pre-requisite id is invalid or not found'}
However, if I use the imdb id, it seems to be working. If their is such a TMDB id, why would the lookup by that id fail? This seems like a bug.
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 Dale
on July 22, 2013 at 5:53 AM
It might be that someone searched for that ID before the cache server cached it. Wait for 24 hours when the cache is flushed, I think its 24 hours.
Dale.
Reply by Travis Bell
on July 22, 2013 at 10:18 AM
Hi johnb003,
The current id 208983 (as of 8:19 AM MST this morning) seems to be returning data:
Do you have another example?
It is indeed like what Dale said though. 404 pages are not supposed to be cached but there is clearly a bug lurking around there somewhere that is causing them to be.
Reply by johnb003
on July 22, 2013 at 9:01 PM
So here's what I get from my python shell, note the id returned, and passed in.
Reply by Dale
on July 23, 2013 at 3:19 AM
Yea I have checked the API still needs some time to clear it's cache. Travis might be able to help it alone.
Dale/
Reply by johnb003
on July 24, 2013 at 5:00 PM
Clearing the cache seems like a short term solution. Perhaps ids > latest can be prevented from caching at all.
Reply by Travis Bell
on July 24, 2013 at 5:41 PM
That's how it's supposed to work but like I mention above, there's a bug in there somewhere that isn't actually working.
Reply by luigi.coluccio
on July 31, 2013 at 5:40 AM
Hi, the issue is still open.
this call doesn't work. http://api.themoviedb.org/3/movie/4258?api_key=APY_KEY
{"statuscode":6,"statusmessage":"Invalid id - The pre-requisite id is invalid or not found"}
this call work: http://api.themoviedb.org/3/movie/04258?api_key=APY_KEY
the ID field must be not less 5 numbers now?
Reply by Travis Bell
on July 31, 2013 at 9:05 AM
With regards to Scary Movie 5 (4258), please see this thread: https://www.themoviedb.org/talk/51f811c819c2953a8928df8c
Reply by luigi.coluccio
on July 31, 2013 at 9:14 AM
Ah ok. Thanks for the quickly reply. Regards
Reply by matthewbuchanan
on September 18, 2013 at 7:30 AM
Travis, any update on this caching bug? It still appears to be an issue; I’m fielding queries from our members frustrated that new films they add to TMDb aren’t immediately available for import via the API, as they used to be under 2.1.
Reply by Travis Bell
on September 18, 2013 at 10:05 AM
Hey guys,
I've created a new ticket for this here. I'm in the middle of some feature work that needs to get done and I don't imagine finding time to look at anything else until it's completed in ~2 weeks. I'll make sure to take a look at it then.
Cheers.
Reply by matthewbuchanan
on September 18, 2013 at 12:33 PM
Thanks Travis.
Reply by Travis Bell
on October 11, 2013 at 1:24 PM
The fix for this was just pushed live. Already cached items won't show any difference but as they expire, no new invalid ids should be cached.Had to revert it for the time being, I will work on this next week.
Reply by letterboxd
on October 13, 2013 at 8:23 PM
Oh no! I feel your pain, Travis. Caching is a harsh mistress. I wish you luck!