| 1 |
README file for the OG Public Access Drupal module.
|
| 2 |
|
| 3 |
|
| 4 |
Description
|
| 5 |
***********
|
| 6 |
|
| 7 |
The OG Public Access module allows Organic Groups (OG) administrators to control
|
| 8 |
public access to their groups' content. This module does not require group
|
| 9 |
administrators to be granted the site-wide "administer nodes" permission.
|
| 10 |
|
| 11 |
The use case targeted by this module is for a site to have teams of writers
|
| 12 |
submitting content privately in their groups, with editors controlling what is
|
| 13 |
allowed to go public in specific groups.
|
| 14 |
|
| 15 |
The workflow is very similar to Modr8's [http://drupal.org/project/modr8].
|
| 16 |
|
| 17 |
If all the group administrators have the "administer nodes" permission, you do
|
| 18 |
not need the OG Public Access module. Modr8 would do fine.
|
| 19 |
|
| 20 |
OG Public Access works by manipulating data in the node_access table. I'd be
|
| 21 |
glad to get feedback from the community about the way this module plays with
|
| 22 |
node_access. Porting this to Drupal 5.x will probably require some
|
| 23 |
re-thinking... Contributions are welcome!
|
| 24 |
|
| 25 |
|
| 26 |
Installation and configuration
|
| 27 |
******************************
|
| 28 |
|
| 29 |
1. Copy the 'og_public_access' directory and its content into your Drupal
|
| 30 |
modules directory.
|
| 31 |
|
| 32 |
2. Grant the "moderate public access to content in groups administered by self"
|
| 33 |
permission to appropriate roles. Users will need to have an administrator
|
| 34 |
status in their groups to be able to moderate public access to content in
|
| 35 |
those groups.
|
| 36 |
|
| 37 |
3. If your group administrators do not have the "administer nodes" permission,
|
| 38 |
then you'll have to set these defaults to node types used in groups
|
| 39 |
(admin/settings/content-types):
|
| 40 |
|
| 41 |
* Published: Yes
|
| 42 |
* In moderation: No
|
| 43 |
|
| 44 |
You need this, unless you want people with "administer nodes" permission to
|
| 45 |
also have to go through every node to publish them.
|
| 46 |
|
| 47 |
4. In the Organic Groups settings (admin/settings/og), select "Visible only
|
| 48 |
within the targeted groups" in the "Visibility of posts" section.
|
| 49 |
|
| 50 |
5. [Optional] Configure the behavior of og_public_access to your liking in its
|
| 51 |
settings page (admin/settings/og_public_access).
|
| 52 |
|
| 53 |
|
| 54 |
Usage
|
| 55 |
*****
|
| 56 |
|
| 57 |
Group subscribers can create content as usual.
|
| 58 |
|
| 59 |
Group administrators should go to "moderate public access to group content"
|
| 60 |
(admin/og_public_access/moderate) to grant public access to new posts in any of
|
| 61 |
their groups. For each group into which the content has been posted and for
|
| 62 |
which the user is an administrator, the user is given the choice to approve,
|
| 63 |
reject or do nothing.
|
| 64 |
|
| 65 |
Approving a post makes it accessible to non-subscribers of the group. Rejecting
|
| 66 |
removes it from the group (but does not delete it). Doing nothing leaves the
|
| 67 |
post in the queue for later approval, and also leaves it accessible to group
|
| 68 |
subscribers.
|
| 69 |
|
| 70 |
|
| 71 |
Caveats
|
| 72 |
*******
|
| 73 |
|
| 74 |
When a post is rejected from each of the groups it had originally been posted
|
| 75 |
to, it remains in the system but is no longer associated to any group and is
|
| 76 |
accessible only to users with "administer nodes" permission.
|
| 77 |
|
| 78 |
|
| 79 |
Credits
|
| 80 |
*******
|
| 81 |
|
| 82 |
David Lesieur, http://davidlesieur.com.
|
| 83 |
|
| 84 |
This module was developed for a client of Koumbit.org (http://koumbit.org).
|
Parent Directory
| 
Revision Log
| 
Revision Graph