When I use the other Search functions, and view different pages, then even after I pass the end (view page: total_pages + 1), I get a total_pages value that is not 0 (an actual page number). However, with TV searching, when I pass the end, it shows 0 as the total page number.
Could this be fixed, so that all the search functions have the same way of working?
Es fehlt ein Film oder eine Serie? Logge dich ein zum Ergänzen.
Diesen Eintrag bewerten oder zu einer Liste hinzufügen?
Kein Mitglied?
Antwort von Travis Bell
am 19. April 2014 um 10:53
Hi Mike,
I'm getting the same behaviour on both movie and TV searches:
Both return:
Can you give me an example of what you mean?
Antwort von LordMike
am 19. April 2014 um 12:01
I must have been tired. I just ran through my tests again and found that your'e right about Movie searching. I must have been thinking of it, but meant something else. Because what I can see is that these are giving the results I talked about:
As total_pages equals 0 is now the expected value, I have found that List, Tv , Person and Movie behave as expected. These give other results:
But I must say, I rather better like the idea that it's returning useful data for those high(er) pagecounts.
-Mike
Antwort von Travis Bell
am 20. April 2014 um 10:19
Hey Mike,
I see the consistency you're talking about. IMO, the way company/keyword/collections work should the the way everything works. I'm not sure where movie and TV is different but I'l probably end up fixing it so it's the same everywhere.
I've created a new ticket for this here.
Antwort von Travis Bell
am 28. April 2014 um 15:25
The fix for this is now live, everything should be consistent now. If you spot one that isn't, let me know.
Antwort von LordMike
am 28. April 2014 um 15:50
All our unit tests pass through now. Seems to work :)
(Sorry, I reopened the thread)
Antwort von LordMike
am 28. April 2014 um 16:04
I might have been too quick, seems the caching is messing with me, the following three requests exhibit different results:
I can see in the headers of the response, that the first request s significantly newer than the other two:
Vs.
This might indicate a cache purging mechanism that doesn't account for the missing page parameter (or I'm just very unlucky :))
Antwort von Travis Bell
am 28. April 2014 um 16:11
Hey Mike,
Heh, yes, you will have to wait for the caches to expire. On a related note, there will always be the potential that when pages are cached, new items could be added that would not get reflected in any counts or results until the cache expires. I believe the genre pages are cached for 6 hours (you can see the time the object will expire with the
X-Memc-Expires
header).Cheers.
Antwort von LordMike
am 28. April 2014 um 16:19
Of course, I was just worried that you may have had a pre-fetching service which populated the cache. The ½-hour gap (the time before the other two expired) may have indicated that something wasn't being fetched correctly.
I'll manage :)