I downloaded the latest version from CVS (nodeaccess.module,v 1.4.2.7.2.7 2007/04/30 19:35:18 debtman7 ) but
I still get the same issue. Any changes I have made to grants for the node has no effect. Everyone who normally is given
access to a node via admin/user/access can view, edit, and delete the node independent of any settings I make for nodeaccess.

Add-on Modules Installed:
ldapauth (there are no users except ldap users)
cck
views
casetracker

I'm trying diagnostics - but haven't found a reason why its not working. Any advice to track this down would be helpful.

Comments

firebus’s picture

firebus commented

subscribing (same problem for me)

firebus’s picture

firebus commented
Status: Active » Fixed

okay. i figured this one out.

i was getting the grant all row in my node_access table on node_rebuild.

this is because i had a bogus node in the node table.

i'm not exactly sure what was wrong with this node, but it had been deleted uncleanly. there was still a row in the node table for it, but it wasn't viewable on the site - i got those nice "your argument to foreach() is not an array" type errors.

deleting that row from the node table fixed this problem, however it gave me another :) now all my content is invisible to the anon user, even ones that should be. i'll move over to that issue in the queue and babble a little more.

you can troubleshoot this to see if you have the same problem by:
-watching the query log while running 'rebuild permissions' in the 'post settings' page
-adding some error_log functions to the node_acquire_grants function and whill running 'rebuild permissions'

firebus’s picture

firebus commented

after removing the offending node, i had to go back to the nodeaccess settings page and resave my grants. happiness ensued.

firebus’s picture

firebus commented
Assigned: Unassigned » firebus

assigning to me. bug me if you're still having trouble with this.

rar’s picture

rar commented

-watching the query log while running 'rebuild permissions' in the 'post settings' page

Where do I find the rebuild permissions in the 'post settings' page? I can't find that.

I did fix the problem by starting over completely from scratch with a new database, but I'd like
to try to "rebuild permissions" you mentioned on the old one.

Thanks!

rar’s picture

rar commented

Nevermind the question - I found it

/admin/content/node-settings

Anonymous’s picture

Anonymous (not verified) commented

Well that's good to know, unfortunately I can't think of anything I can do in this module to deal with such a problem so it'll just have to stand... You might want to file a drupal bug report since this would be undesired behavior and it's coming from the core drupal node module.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)