Hello,
The module worked fine for me to limit the edit and delete functions to referenced users.
I want the nodes to be viewed by anonymous users, which work fine when going to the node page directly.
But when I use a view to list the nodes, the list doesn't work for anonymous users when there are more than 1 node to list. If I login as admin and try my view list again, the results come with no problems.
I had to uninstall the module to get back my results for anonymous users, but I will be testing further the problem on a demo version. I also have other content access modules installed, and I think your module might get in conflict with them, but I wanted to know if you have been facing this kind of behaviour before.
I will come back with more details,
Best Regards,
Clem
P.S: Thumbs up for this module, it's one of the most impressive for me.
Comments
Comment #1
danielb commentedViews is possibly caching for anonymous users.
Comment #2
danielb commentedIf you find out it wasn't views caching, please reopen and suggest a fix/patch, otherwise I don't think I've done anything wrong in terms of access.
Comment #4
pixelsweatshop commentedHaving the same issue. Have now uninstalled the module but cannot get my views back that included the content type I used the Node Access User Reference module on. I have rebuilt permissions and flushed cache. Any other suggestions?
P.S. Great module. Would really like ot use it, but its more important that my anonymous users get to see the views. (Only referenced users get to edit/delete)
Comment #5
root66 commentedSame here. I want all anonymous users to view the nodes (in views) and the referenced users to edit them.
Comment #6
danielb commentedThis module never gives access to anyone that isn't assigned through the CCK field. However by giving *someone* access, you remove the default behaviour of drupal that allows anybody to see the node. I cannot assume you want anonymous users, or regular members to have access, and that isn't the job of this module.
You will need to give them access some other way. See the project page of this module for some suggestions.
However this should have nothing to do with views.
Comment #7
danielb commentedI hope my last post has shed some light on the situation.