Content Access Control

Overview

OG Workflow integrates the permission systems of Organic Groups (OG) and Workflow. Permissions for workflow state transitions can be granted based on OG group roles (see screenshot).

7.x-1.x

Use Version 1 for OG 1.x. There is no node access control for this version, but you can use Rules to bind state transitions e.g. to publish/unpublish actions.

7.x-2.x

Version 2 integrates with OG 2.x and is not compatible with OG 1.x. Additionally, it integrates with og_access (part of OG). That means that private entries in groups are respected and people cannot view them even if workflow would allow them (enable strict access control in OG settings).

This module, Node Protection Via Webform, allows you to require people to fill out a form before viewing specific content types on your site. A person need only fill out the form one time, then all other content protected by the module is open to be viewed by the person.

Current situation

Drupal (6.x, 7.x) core module node provides a view which shows a list of all the published nodes:

http://www.example.com/node

Nowadays most Drupal installations use Views, Panels, etc, which are more configurable making this feature useless.

Description

This module adds an administration settings panel to handle /node page access.

Version 7.x-1.x provided "two useful features which Drupal itself is missing: a simple permission to allow downloading of private files by role, plus the ability to combine both public and private downloads".

Version 7.x-2.x removes the "global" permission and implements a per-directory by-user and by-role filter instead, to let the administrator better tweak the whole website and increment the overall security.

This module extends Profile 2 by allowing administrators to create privacy levels as predefined groups or sets of profile fields on a per role basis. Users can then select from among the privacy levels to apply access control to their profile.

Requirements:

Profile 2

A simple module that tracks downloads of files added through CCK/Fields by asking anonymous users to enter their email address. Returning anonymous users are tracked using a cookie. A tracking interface shows email address and user account information for tracked files downloaded on the site.

Why only have users enter their email address? Email addresses are a unique and easy way to identify users, and the barrier for entry is lower than actually registering for the site.

Set up is easy:

With this module you can lock fields in a webform so that those fields cannot be deleted or modified except by administrators with appropriate permissions. It was written to work in tandem with the Webform Default Fields module but is not dependent upon it. The idea is that if you create default fields for a webform, you may want to ensure consistency by preventing webform creators from modifying some or all of the default fields.

This module allows administrators to specify that a user must fill out a form (provide their e-mail address) in order to download a file uploaded using filefield.

When a user clicks on teh file (displayed in the node), they are redirected to a form to fill out, and will then receive an e-mail message with an obscured path to download the file.

This module extends Ubercart product features.

Grant customers access to items like Nodes and CCK fields, Taxonomy, Roles etc. on your site when they purchase specified Ubercart products. Access can be configured to start immediately, after a fixed period from purchase, or on a preset date, and it can be given either for indefinite time, until a preset date or for a limited period based on the feature's settings.

Currently it has nodes and CCK fields handler that uses ACL and Content Access modules.

With future addition of more handler modules, it can grant access to other items (i.e. Taxonomy, Roles).

This project enables comments permissions for referenced nodes on Drupal 7.
Basically if users comment on a node and there is a referenced node, the referenced node can have permissions to only be able to cemmented by users that have previously commented on the first node, you can select on the module configuration the content types options.

Hopefully i can have this module ready by end of year.