The module does the job for new nodes, but when we want to disable the access to an existing node (which was created before enabling Nodeaccess) for anonymous users, this doesn't seem to be applied. Anonymous can still access that node without any hassle.

We've tried every possible configuration throught the UI, to no avail. Permissions are being rebuilt, caches cleared, and so on.

Is there a special procedure in order to achieve this, that isn't mentionned in the readme.txt or through descriptions in the configuration UI?

This is our current configuration of the Nodeaccess module, but as I mentionned: it has been modified multiple times (checked off "Preserve hidden grants", checked "Give node grants priority", added the role "Anonymous users" to the checkable list of an existing node, ...), with everytime the permissions being rebuilt and the cache cleared.

CommentFileSizeAuthor
"Studenten" is the only role that should be able to access the node, yet it's accessible for anonymous users as well?7.91 KBknalstaaf

Comments

vlad.pavlovic’s picture

vlad.pavlovic commented

Just making sure I am thorough in understanding the problem, what are the settings for your individual content type? Are they the same as defaults from above?

knalstaaf’s picture

knalstaaf commented

No, they're not, because some some nodes of this content type should be visible and other shouldn't. This works perfectly for new nodes though. It's not that of a big deal, but just for contribution purposes I'm reporting this issue.

vlad.pavlovic’s picture

vlad.pavlovic commented

So, when you edit the node, it works fine, you are saying that it doesn't go back and edit your existing nodes automatically?

If that's the case, then, I am sorry, but I think that this should be marked as 'works as designed'. I don't think it would be wise to force an overwrite of existing node access permissions.

knalstaaf’s picture

knalstaaf commented

For nodes node that were created after enabling Nodeaccess, it works fine. But it doesn't work out for nodes that already existed before I installed the module. I can configure the permissions for this nodes, but they're not applied apparently. (That's in short what's the issue.)

blackice2999’s picture

blackice2999 commented

Hi,

please try this patch i think it can also solve your problem

#2075033: Access denied for anonymous users

vlad.pavlovic’s picture

vlad.pavlovic commented
Status: Active » Fixed

Pushed to dev version, thank you for your work!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

(not verified) commented
Issue summary: View changes

current config + reproduction