Hi there,

Let me first say this is an awesome module that allows in a simple way to have full control over block caching.

I installed it and ran it without applying the patch and it works fine.

I am very interested in applying the patch but before doing that i would like to know the differences between "with node_access" and "no node_access". The choice is confusing as Drupal makes block caching inactive if u have any node access modules running.

Hope someone can explain this to me.

Cheerz
Rajeev

Comments

swentel’s picture

swentel commented
Status: Active » Fixed

With node_access: install this if you don't have any modules enabled on your site which implement the 'node_grants' hook.
No node access: install this if you have modules implementing that hook. This *could* lead to some side effects depending on what the block is showing. A typical one is the block listing content which is related to a group (from the Organic Groups module) This patch removes the 'count(module_implements('node_grants')' part from block.module so caching can be enabled for blocks.

chweetraju’s picture

chweetraju commented

thanks for your reply.. i am getting a better picture now.

regarding "no node_access": how do u identify user rights for the generated content that is cached? do you store some value in db per block, if so what do u store?

i am eager to know how you solved it and why Drupal didnt think of this earlier.

chweetraju’s picture

chweetraju commented
Status: Fixed » Active
swentel’s picture

swentel commented
Status: Active » Closed (fixed)

Well we don't store anything special, caching is based on the settings of that block (per page and/or per user) flushing of the cache then happens based on other params (node submission, user login/logout etc)