|
1
|
|
|
2
|
Content Access Module
|
|
3
|
-----------------------
|
|
4
|
by Wolfgang Ziegler, nuppla@zites.net
|
|
5
|
|
|
6
|
Yet another node access module.
|
|
7
|
This module allows you to manage permissions for content types by role. It allows you to specifiy
|
|
8
|
custom view, view own, edit, edit own, delete and delete own permissions for each content type.
|
|
9
|
Optionally you can enable per content access settings, so you can customize the access for each
|
|
10
|
content node.
|
|
11
|
|
|
12
|
In particular
|
|
13
|
* it comes with sensible defaults, so you need not configure anything and everything stays working
|
|
14
|
* it is as flexible as you want. It can work with per content type settings, per content node settings
|
|
15
|
as well as with flexible Access Control Lists (with the help of the ACL module).
|
|
16
|
* it trys to reuse existing functionality instead of reimplementing it. So one can install the ACL
|
|
17
|
module and set per user access control settings per content node.
|
|
18
|
Furthermore the module provides conditions and actions for the rules module, which allows one
|
|
19
|
to configure even rule-based access permissions.
|
|
20
|
* it optimizes the written content node grants, so that only the really necessary grants are written.
|
|
21
|
This is important for the performance of your site.
|
|
22
|
* it takes access control as important as it is. E.g. the module has a bunch of simpletests to ensure
|
|
23
|
everything is working right.
|
|
24
|
* it respects and makes use of drupal's built in permissions as far as possible. Which means the
|
|
25
|
access control tab provided by this module takes them into account and provides you a good overview
|
|
26
|
about the really applied access control settings. [1]
|
|
27
|
|
|
28
|
|
|
29
|
So the module is simple to use, but can be configured to provide really fine-grained permissions!
|
|
30
|
|
|
31
|
|
|
32
|
Installation
|
|
33
|
------------
|
|
34
|
* Copy the content access module's directory to your modules directory and activate the module.
|
|
35
|
* Optionally download and install the ACL module too.
|
|
36
|
* Edit a content type at admin/content/types. There will be a new tab "Access Control".
|
|
37
|
|
|
38
|
|
|
39
|
ACL Module
|
|
40
|
-----------
|
|
41
|
You can find the ACL module at http://drupal.org/project/acl. To make use of Access Control Lists
|
|
42
|
you'll need to enable per content node access control settings for a content type. At the access
|
|
43
|
control tab of such a content node you are able to grant view, edit or delete permission for specific
|
|
44
|
users.
|
|
45
|
|
|
46
|
|
|
47
|
Running multiple node access modules on a site (Advanced!)
|
|
48
|
-----------------------------------------------------------
|
|
49
|
A drupal node access module can only grant access to content nodes, but not deny it. So if you
|
|
50
|
are using multiple node access modules, access will be granted to a node as soon as one of the
|
|
51
|
module grants access to it.
|
|
52
|
However you can influence the behaviour by changing the priority of the content access module as
|
|
53
|
drupal applies *only* the grants with the highest priority. So if content access has the highest
|
|
54
|
priority *alone*, only its grants will be applied.
|
|
55
|
|
|
56
|
By default node access modules use priority 0.
|
|
57
|
|
|
58
|
|
|
59
|
|
|
60
|
Footnotes
|
|
61
|
----------
|
|
62
|
|
|
63
|
[1] Note that this overview can't take other modules into account, which might also alter node access.
|
|
64
|
If you have multiple modules installed that alter node access, read the paragraph about "Running
|
|
65
|
multiple node access modules on a site".
|
