There does not seem to be support for using Views block cache when using this module. Is it feasible to add this feature? It is my understanding that Views will generate a different cache ID for each different contextual filter setting. However, this module acts as a default for the contextual filter when none is supplied. So, if you try to use block caching with a global filter, only one result will be cached for all of the filter combinations (as the contextual filter is never actually set).

Would it be possible to hook into the cache ID generation process to create a unique key for each global filter combination that is used? I assume time-based caching still works properly (I haven't noticed any issues with using it and this module together).

I should clarify that I'm trying to use the "global" block cache setting. We have thousands of users, so caching per user isn't feasible. Also, many users will set their global filters the same, and it would be nice to have it stored in cache once for all of them.

Comments

byrond’s picture

Issue summary: View changes
RdeBoer’s picture

Hi byrond,
Thanks for the suggestion.

"... many users will set their global filters the same, and it would be nice to have it stored in cache once for all of them"

Interesting thought. Don't have the bandwidth right now, but I like the idea...

Rik

RdeBoer’s picture

Thinking about this a bit more

"We have thousands of users, so caching per user isn't feasible."

Maybe, although the amount of data stored per user can be very small. I mean essentially for each user it is just a number (like a drop-down select option code), right?

And if you store this info by option code, which is what I think you suggest, and internally keep track of all the users using each opiton, would that not be the same amount of data? Except that the matrix is transposed?