Hi, and thank you for this module!
While using the module I noticed that the views caches don't get refreshed if I use custom caching with cacherouter (and I guess its the same for memcache api).
In my case I was using cacherouter with apc as default backend - which resulted in me seeing the same view despite me having altered nodes that were supposed to refresh the views. When I switched the cache back to normal (="db"), the view worked as expected.
As far as I know, any custom cache should work if you use the cache_clear_all()-function, instead of custom SQL-queries.
So, is it that simple, or would it not work? If it is, will there possible be support for cacherouter?
Comments
Comment #1
bibo commentedCould someone more knowledgeable comment on the doability of this? Is there a reason why this module couldn't possibly use cache_clear_all() for the cacheclearing? What have I missed?
This module is fantastic anyway, but with APC/Memcache-support it would be really fantastic^2. Or something :)
Comment #2
steven jones commentedI don't think we actually attempt to clear the views_cache tables?
Can you point me at the code where we should be using
cache_clear_all()?Comment #3
steven jones commentedClosing as info not privided
Comment #4
pvaling commentedWas wrong cause views_cache_content is not cache system table. issue need to be closed...
Comment #5
pvaling commented