Hi I've created 2 sites using the content_access modules, both about a year ago. When I tested at the time the module was working perfect. But over the past 6 months 1 site was having issues with not writing to the node_access table after a node has been edit/updated. For a work around I've been adding the records manually into the node_access table, since this site doesn't have new content.

The second site is now experiencing the same issue, there is much more content being updates and added so the issue is more serious.

I'm not sure if its a content access issue, an ACL issue or node module issue.

I've pin pointed that on line 665 of the node module that node_access_acquire_grants doesn't write to the node access table.

any help would be appreciated.

Cheers

Comments

jump_howhigh’s picture

jump_howhigh commented

I've been debugging more about this issue. And what I found was in the content_access_node_access_records hook. the conditional statement that checks:

else if ($optimize && content_access_optimize_grants($grants, $node)) {

cause the grant variable to be emptied. Before it hits this line the array is good.

So I set $optimize = FALSE as the default. This has fixed my issue for the time being but I hope there's a better solution.

fago’s picture

fago
Primary language German
Location Vienna
commented
Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)

Please test the latest version. Are you using any other node access modules?

Setting down priority as it looks like you are the only one experiencing this.

oldphotos’s picture

oldphotos commented
Version: 5.x-1.3 » 5.x-1.4

I'm using version 5.x-1.4 and I have what is probably the same issue.

With content access enabled, anonymous users cannot view the new content (despite the access rules).

When I disable the module, anonymous viewing is fine.

fago’s picture

fago
Primary language German
Location Vienna
commented

hm, for me everything seems to be working fine. Again, please test the latest version and report whether you are using any other node access modules?

ycimlynn’s picture

ycimlynn commented

I need to jump on this bandwagon. I am having the same issue. I have used this module forever, and now it is no longer working. Everytime a user edits their page, you can no longer view this page.

Not sure what started the issue.

It deletes the entry from the node_access table.

Any clues what might be causing this? Where to start looking?

I updated to the latest version 5x-1.5.

pianomansam’s picture

pianomansam commented
Version: 5.x-1.4 » 5.x-1.5
Priority: Normal » Critical
Status: Postponed (maintainer needs more info) » Active

I am experiencing similar problems. My individual node "Role access control settings" are not being saved. This makes per node per role permissions impossible with this module. Please help!

salvis’s picture

salvis
he/his
commented

Have you disabled the ACL module?

pianomansam’s picture

pianomansam commented

I had this issue even before I installed the ACL module. I then installed it to see if it would work, but no results.

fago’s picture

fago
Primary language German
Location Vienna
commented
Category: bug » support
Status: Active » Closed (works as designed)

This ususally happens if a module interrupts the page flow on nodeapi insert/update, e.g. use the trigger module + the page redirect or rules + forcing the immediate redirect does that. This is a problem of the module triggering the redirect, but not of content access.