Content Access Control

This simple module allows nodes with required elements to be left empty when the node is in selected workflow states.

This is Useful for 'draft', 'unpublished' or 'staging' kind of workflow states where the node isn't yet finished. It's especially useful when using nodes as complex formal applications over several pages where users typically spend lot of time to fill out and work with them.

The FAPI '#required' attribute will recursively be unset after the form is build, but enabled again just before rendering, giving the user the same visual experience as before.

Prevent access to OG private posts except to privileged users and OG group members.

This module serves to ensure that OG private posts remain private to the Organic Group(s) to which they're posted, regardless of which other modules may be trying to grant access.

Rationale

Under most circumstances and for most simple Drupal installations, Organic Groups will do a fine job of ensuring that group posts marked "private" will only be accessible by group members. It does this by simply refusing to grant access to those nodes.

Overview

This module grants per-session permissions for users to access nodes they created.

Yet another simple node access module, this time catering to users whose nodes have to be published for them to have access.
It grants temporary (session based) node access permissions to users with set
roles after they create that node.

This module provides new permissions to allow update access to users for orders with specific statuses and attempts to solve this issue. It also allows you to control which statuses the user is allowed to change an order to.

Description

The field group access module allows a site builder to hide any field group based on a ctools access rule.

Dependencies

• Ctools
• Field Group

Overview

This module will count the number of times an authenticated user visits a page matching a path pattern. If the views per hour reach the established limit the user will be redirected to either an established page or a will be sent to the standard 403 page.

Permissions exist to allow roles to ignore the limits so administrators can browse without limitation.

Use Cases

The use case I initially built this for is to deter users from manually scraping through other user's profiles to build mailing lists.

This plugin allows developers to integrate Latch on his/her drupal service. Latch is a service that lets end-users add an extra level of security to their online accounts and services.
With this version of the plugin, developers can pair and unpair users and check their latches status. For more information please visit https://latch.elevenpaths.com or the plugin page on https://github.com/ElevenPaths/latch-plugin-drupal7

This plugin allows developers to integrate Latch on his/her Drupal service. Latch is a service that lets end-users add an extra level of security to their online accounts and services.
With this version of the plugin, developers can pair and unpair users and check their latches status. For more information please visit https://latch.elevenpaths.com or the SDK page on GitHub; https://github.com/ElevenPaths/latch-plugin-drupal6

Overview

This module adds Entity lock support to the community module called content_lock that will prevent two users from editing the same node concurrently. This module exposes the locking node content type of content_lock through all entity, so that content locking can be done over all entity content type.

Features

This module exposes the operations of content_lock module for Entity Content type.

Requirements