Closed (fixed)
Project:
Block Cache Alter
Version:
6.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
7 Dec 2010 at 09:25 UTC
Updated:
21 Dec 2010 at 10:50 UTC
hello
first question: after installing the module, most of my blocks are showing: "No caching".
Sets the blockcache alter module this setting or is this the system default?
means: if i turn on the drupal blockcaching without this module, in reality the most blocks are not cached?
second question: if i say for example in views: cache time based for 1 hour - the same block in the block administration says to me: "no caching". does the views option means something different?
if yes -> what does it mean ralated to this module?
thanks momper
Comments
Comment #1
swentel commented1) Most blocks do not have caching by default, so that's normal
2) Views based time caching is not related to block caching - there is a block cache setting in views that syncs though with the block cache settings though.
Comment #2
momper commentedswentel - thank you very much for the fast answer ...
1) ok i see, so this module is really, really useful for me :) (should be in core?)
2) can i understand it like this: if i say "cache time based for 1 hour" in views, views will make a new query after one hour - blockcache alter will independantly recreate the block cache for this block for example after a "node add" immediately -> but views will output the same query like before the new node was added and nothing is changing in the display of the block ...
this is not happening because you sync it smarter?
Comment #3
swentel commentedas for 2) yes - the time based caching will pick up a new version of the the block because that will be recreated by another process - however, the views caching might still contain stale data of course.