| 1 |
********************************************************************
|
| 2 |
D R U P A L M O D U L E
|
| 3 |
********************************************************************
|
| 4 |
Name: Nodeperm_role module
|
| 5 |
Author: Matt Westgate <drupal at asitis dot org>
|
| 6 |
Author: Robb Canfield
|
| 7 |
Last update: (See CHANGELOG.txt for details)
|
| 8 |
Drupal: 4.7
|
| 9 |
Dependencies: node.module
|
| 10 |
********************************************************************
|
| 11 |
|
| 12 |
INSTALLATION:
|
| 13 |
********************************************************************
|
| 14 |
1. Place the entire nodeperm_role directory into your Drupal modules/
|
| 15 |
directory.
|
| 16 |
|
| 17 |
2. Enable this module by navigating to:
|
| 18 |
|
| 19 |
administer > modules
|
| 20 |
|
| 21 |
3. You must configure this module by navigating to:
|
| 22 |
|
| 23 |
administer > settings > nodeperm_role
|
| 24 |
|
| 25 |
IMPORTANT! After you've backed up your database, click the
|
| 26 |
'Enable nodeperm_role' button to automatically configure the
|
| 27 |
Drupal database to use this permissions system.
|
| 28 |
|
| 29 |
|
| 30 |
WORKING WITH THE ACTIONS MODULE:
|
| 31 |
********************************************************************
|
| 32 |
|
| 33 |
** Not enabled at this time **
|
| 34 |
|
| 35 |
When both actions (http://drupal.org/node/16013) and nodeperm_role
|
| 36 |
module are enabled, Drupal will find and install a new action to
|
| 37 |
change role-base viewing and editing permissions. Navigate to
|
| 38 |
your actions listing page and choose the 'Change role-based
|
| 39 |
permissions' action to start using it.
|
| 40 |
|
| 41 |
Now add workflow module to the mix (http://drupal.org/project/workflow)
|
| 42 |
and node permissions can be set to automatically change when a node
|
| 43 |
state changes (for example you could disable all editing permissions
|
| 44 |
when a node's workflow state is published).
|
| 45 |
|
| 46 |
FINAL COMMENTS
|
| 47 |
********************************************************************
|
| 48 |
|
| 49 |
- If you are using actions to unpublish nodes, and you want authors
|
| 50 |
to be able to edit their content easily, Install the workspace
|
| 51 |
module (http://drupal.org/project/workspace) which will list all
|
| 52 |
nodes (even unpublished ones) an author owns.
|
| 53 |
|
| 54 |
- If an user has 'edit own foo' permission, where 'foo' is the name
|
| 55 |
of a node type (e.g., page, story, blog), then that permission
|
| 56 |
overrides any node level permission in effect.
|
| 57 |
|
| 58 |
- Regarding the 'edit own node permissions' permission. If an
|
| 59 |
user isn't allowed to 'edit their own node permissions' (and they
|
| 60 |
also don't have 'administer nodes'), then by default no viewing
|
| 61 |
or editing permissions will be assigned for that node. Only users
|
| 62 |
with 'administer nodes' will be allowed to edit the node. The
|
| 63 |
original author may be able to edit their entry if he/she has an
|
| 64 |
'edit own foo' permission (See previous comment).
|
| 65 |
|
| 66 |
To summarize, it's best to disallow a role to 'edit own node
|
| 67 |
permissions' when A) you want user's with 'administer nodes' to
|
| 68 |
control all permissions or B) actions module is automatically
|
| 69 |
handling permissions assignment or C) some combination of A and B.
|
| 70 |
|
| 71 |
- When setting up your permissions workflows, it's helpful to login as
|
| 72 |
an user with limited privileges in one browser while staying logged
|
| 73 |
in as admin in a completely different browser. This way you can
|
| 74 |
watch the Drupal logs and inspect the content submitted by the
|
| 75 |
restricted user.
|
Parent Directory
| 
Revision Log
| 
Revision Graph