This was supposed to be the next ‘feature’, I have already started a version of this a while now. It got sidetracked with the translation issues to fix. In any case, this needs to be done first and foremost to lighten the load of the very nice folks at TMDB who make this plugin possible in the first place.
It has been in the books since the beginning. Originally I opted not to do so because of a paragraph in the terms of use of the TMDB API which stated something like “no contents shall be stored in one’s db other than for caching purposes”. So I pushed back, wanting to make sure that the way it was handled would be in line with the TMDB terms.
The way this will work is that the payload will be cached in the db for a certain amount of time. There may or may not be a setting to allow a user to determine that amount of time. Then for the front end this will be applied automatically: When there is a request, the plugin will check if a cached version exists else it will call TMDB and then cache it. What I haven’t figured out completely is the wordpress backend behavior. To keep things simple, the admin will perhaps always get a ‘fresh’ view (that is then cached too). I thought of the admin being able to potentially compare the cached version to a fresh one and decide which to keep, but it seems a little more than I have time for right now.
