Closed (won't fix)
Project:
Nodeaccess
Version:
6.x-1.2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Nov 2008 at 09:18 UTC
Updated:
17 Feb 2011 at 22:22 UTC
Jump to comment: Most recent
We have two roles: documentation-builders and customers. The documentation-builders want to hide some content from the customers, but they want some contents to be editable by the customers. The hiding part can be done with the nodeaccess.module - but how should we do the latter? Well, this is what the attached patch does.
Detailed description of the problem is available: http://kybest.hu/en/blog/default-permissions-nodeaccess-module
| Comment | File | Size | Author |
|---|---|---|---|
| nodeaccess-default-permissions.patch | 4.18 KB | boobaa |
Comments
Comment #1
Anonymous (not verified) commentedI think I see what you're getting at here, but I think it's a bit limited use. From what I get the basic idea is to be able to set one default permission for existing content and one for newly created content. While this is a bit of a shortcut I think it also introduces some confusion about what the options do and what exactly will happen with new vs existing content.
Comment #2
zohera commentedNo display of node even by granting view permission using nodeaccess module , untill and unless access node in permission page is set for anonymous users.Is there any solution to grant view permission to a node using nodeaccess module without setting default access node permission in permissions page in usermanagement.
Comment #3
zohera commentedis it possible to grant view permission to one node and disable that permission to another node for same
content type and same role but for different content using node access module.
Comment #4
Anonymous (not verified) commented