I'm attempting to use Node Access to solve the following problem: By default, all nodes of a given content type need to be editable by my authenticated user role. However, in specific cases, individual nodes should be locked down so that only a single user can edit them.

So, I'm using Node Access. I set the defaults on the Permissions tab for the content type to allow authenticated users to edit. Then I went to the Permissions tab for the specific node in that content type, chose my user under Grant Update Access, unchecked authenticated user under Role Access Control Settings, and saved. After the save, authenticated user came back as checked, and it looks like there's no way to get rid of it.

So, is what I'm trying to do even possible? Could it be some configuration issue I'm overlooking? Any advice or guidance you could provide would be welcome.

Comments

WisTex’s picture

WisTex CreditAttribution: WisTex commented

Yes, I noticed that problem too, and this is the only workaround that I can find.

1.) Add another role in Roles.
2.) Uncheck authenticated users and check the new role you created.

If you do this, the change will stick. But there is still a problem. You have to edit EVERY SINGLE PAGE to change the permissions, and all new pages automatically get the permissions set to editable to anyone who creates an account. Now, if your purpose was to have a wiki, then that would be okay, but as it is now, basically its a giant security hole.

WisTex’s picture

WisTex CreditAttribution: WisTex commented

It appears to override all permissions in the permissions page.

For example, if you have it set in the permissions page that users cannot edit other people's forum posts, by default, this module will override that and give EVERYONE with an account EDIT access to ALL posts on the forum!

It also appears to ignore its own settings, surprisingly. Only one role was assigned "edit node content" permissions for the "Node-Access" module, yet any authenticated user can edit even though that check box is not checked.

WisTex’s picture

WisTex CreditAttribution: WisTex commented

Found where you can set the defaults:

/admin/content/types/nodeaccess

The configuration menu for this module appears as a tab on the Content Types page.

That does not fix the problem we have, but it should help you change the default for future pages.

emptyvoid’s picture

emptyvoid CreditAttribution: emptyvoid commented
Component: Miscellaneous » Documentation
nsputnik’s picture

nsputnik CreditAttribution: nsputnik commented

So many other modules to contend with roles and permission. This should take all of that into account and have some sort of priority setting so you could hierarchiz all of them.

sinasalek’s picture

sinasalek CreditAttribution: sinasalek commented
Version: 6.x-1.7 » 6.x-1.8

Same problem here.

emptyvoid’s picture

emptyvoid CreditAttribution: emptyvoid commented

Oh I agree, that is why I plan to leverage the acl module in D7 as it does just what you are describing.

axxint’s picture

axxint CreditAttribution: axxint commented

I ran into a similar problem with a Node Access and Workflow permission conflict. You can try setting module priorities in D6 via PHPMyAdmin / the "system" table of your database (http://drupal.org/node/77674, http://drupal.org/node/278306), though I did this and it didn't work for me. But it might work with whatever particular modules you're working with.