Linux/Apache/PHP 5.2.4

This came up post-production: When an administrator changes the permissions on a node, they won't "take" (node will still display according to old permissions) until the permissions are rebuilt. Is this related to the performance settings (e.g. some form of caching)? I tried disabling page compression to no avail. This is a concern since privacy is imperative and my client can't be expected to remember to rebuild the permissions whenever he/she adds or edits a restricted-access page.

Thanks in advance!

Comments

Ellen Dee’s picture

Ellen Dee CreditAttribution: Ellen Dee commented

Hate hate hate to do it, but I modified node_access_page_submit() in node_access.module to force cache tables to be cleared. If anyone has a better idea, I'd be happy to hear it. Or maybe this is something that should be considered for permanent inclusion? Makes perfect sense to me, but I could be missing something.

Line 787:
+ cache_clear_all();

emptyvoid’s picture

emptyvoid CreditAttribution: emptyvoid commented
Component: Miscellaneous » Code
Assigned: Unassigned » emptyvoid

Thanks for bringing this up, there recall reading changes to how menu and nodes access security function based on updates after the release of Drupal 6.4 This may be required I will have to test it to determine if indeed this is the case.

emptyvoid’s picture

emptyvoid CreditAttribution: emptyvoid commented
Status: Active » Patch (to be ported)

I have committed the change to the dev branch for testing.