Content Access Control

Mark content as restricted so a permission is needed to view it.

Each content type has a permission to view restricted nodes of that type. There is also a global View all restricted content permission.

Each content type may be set to always or never restricted, restricted by default, or not restricted by default. The first two options just apply globally. The second two create a checkbox on each node form, but control its default value differently.

This modules allows users to login to from Drupal into Blackboard without re-entering authentication credentials. The Drupal session is recognized in Blackboard.

After much consideration, I've decided to scrap this module and take the project in a different (and, I hope, far better) direction as Access Control Kit. No further development will be done on Conditional Roles, other than to provide a migration path to ACK.

This is a very simple module that provides a CTools access plugin for using the access rules of another path. It does nothing without the CTools module.

When creating a custom page with Page Manager (for example, a Panels page), this module adds the 'Access to another path' access plugin in the Access tab. You may use it to mirror the access rules used by another path. For example, you might set up a custom search page, and use the access rules for the default Drupal search page, 'search'.

This is the new sandbox for As If.

Audience provides an abstract definition of user groups and types in a given context. These definitions are called "Audience presets" and can be used by other modules to control different types of audience related actions or permissions. By using CTools these audience presets are exportables and can either get stored in a database or live in code provided by modules.

Modules that allows authors to set a limit on the number of times a visitor can view the node within a given timeframe.

When a visitor exceeds the threshold, he will be redirected to another page (configurable) and a message will be set to the visitor that states when he can access the node again.

Build upon Drupal's flooding system.

NOTE: this is sandbox project for me to get acquianted with some api's. I don't intend to release it as a module.

For Drupal 6 (might work for D7?)
The Custom Node Access module provides hook_node_access_custom().

Add custom access callbacks to node/[nid]

Example:

function mymodule_node_access_custom($node, $op, $account) {
  // Grant random access
  return rand(0,1) ? TRUE : FALSE;
}

Credits

This module was sponsored by Berlingske Media A/S

This module provides a context reaction that will restrict access by role. If the current user triggers a context condition that uses this reaction they will either receive an access denied message or be redirected (based on reaction configuration). This module is still under heavy development but is actively being used.

A few use cases.

1. A site op only wishes to have authenticated users access the members/* path. Using this module one would create a path based context then disallow users in the anonymous role to access that path.

Allows administrators to override the visibility of menu items. Normally, items which are inaccessible won't show up in the menu. Using this module, menu items can be set to always show up. Their contents will still be restricted.

See:
http://drupal.org/node/724978
http://drupal.org/node/723964
http://drupal.org/node/300607