535 Modules match your search

Extend and customize Drupal functionality with contributed modules. If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.

Total Moderation Control

This module provides integration between Workbench moderation module and Total Control admin dashboard.

  • It provides content panes for the dashboard based on moderation.
  • It changes the view paths so that they work with total control instead of workbench.

Downloads

Limit Visit

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.

Downloads

Og comments access

Og comments access allow you to manage comment access in Organic group context.

It comes with new og permissions :

  1. Administer OG comments
  2. Modify any OG comments
  3. Delete own OG comments
  4. Post OG comments

With these permissions, you can now restrict comment posting on group.
You can also allow particular OG role to modify all group comments.

These permissions overwrite the global Drupal permission in the group context.

Downloads

Domain Override

Allows overriding page nodes on a domain-specific basis.

Features

  • Provides an "Override" tab on node pages that removes the current domain from the node's domain access, clones the node, and publishes the clone to only the current domain.
  • Copies translations of the node being overridden (if any), too, so they're considered translations of the newly created node.
  • Sidesteps need to use multiple url_alias tables (with Domain Prefix). Makes Drupal interpret the URL alias for a node that's been overridden as a path to this domain's version of the node. Example: node 1 (the node at node/1) is published to all domains with the URL alias contact-us. You visit the node from the subdomain "cats" and select the "Override" tab. Now a new node has been created (node 2), that's published only to the "cats" subdomain, and node 1 is no longer published to the "cats" subdomain. When you visit http://site/contact-us you'll see the content of node 1. However, when you visit http://cats.site/contact-us, you'll see the content of node 2 -- node 1's override.

Downloads

"Premium" Node Access

Control and track "access" to content.

This module allows you adjust content layouts and access by requiring registration (or re-submission) of user details to a CRM.

Upon registering, a user session detail is recorded for the premium access. This can used with the provided Context condition to alter the specific node page and reveal additional blocks and fields.

Downloads

Nodelocks

Nodelocks prevents any user from deleting a node if that node has been added to a list of "locked" nodes.

This module serves as a lightweight alternative to Content Access, which can be configured to prevent the deletion of certain nodes, along with much more functionality.

Downloads

Access Private

This module allow accessing private nodes with a direct link.

Downloads

Domain ip

Domain_ip local tab

We recently saw a scenario where the client wanted to create an ip whitelist for their intranet site. This site is the same installation as the client’s public site. It simply has a different domain and different content. The question was ‘How we can manage separate whitelists and blacklists (ie ‘list sets’) for each domain, rather than one list set per installation.’

This module solves that issue. It is functionally a combination of two existing modules: ‘Ip_ranges’ ( http://drupal.org/project/ip_ranges ) and ‘domain_access’ (http://drupal.org/project/domain).
Domain_ip depends on Domain Access.

Domain_ip behaves similarly to ip_ranges, but it differs in the following ways:

  • Ip_ranges is used to define an ip whitelist and blacklist for a specific site. This is okay except for installations that also use the domain_access module, because they have different domains for a same installation. In this case, they are restricted to single list sets across domains. Whereas ip_ranges works against all domains for an installation, domain_ip provides a separate list set for each domain, respectively, meaning each domain has its own independent whitelist and blacklist.
  • To manage multiple sites, on the administration page there is a separate ip settings tab for each list set. Each domain has its own administration tab.

Downloads

Shared Access

The goal of this project is to provide a method for users to easily configure access settings to their own entities. The interface for configuring access will come from a shared access field attached to the entity.

Development Roadmap

  1. Implement field hooks to define the new shared_access field type.
  2. Define formatters and formatter settings.
  3. Define widgets.
  4. Implement an extendible access controller class structure for defining access realms and their underlying functionality.
  5. Define several default access realms (user, organic groups ... perhaps a few more).
  6. Implement field hooks so that a form shows up on the entity content page.
  7. Implement a standard sharing settings form that can hook into the access controller classes and be used to control access to the entity.
  8. Provide autocomplete functions and hooks for displaying user name/og suggestions as the user types
  9. Implement access hooks and query/query_HOOK alter functions to control access
  10. Implement field access hooks so that the form only shows when the owner or configured admins view the page.

Downloads

Read only node

The read only node module is allow you to set a node as read only by adding a new "Publishing option".
The module commes with 4 new permission :

  • set node as read only
  • set node stiky
  • set node status
  • set node promote

When a node is set as Read only, only the role with the permission 'set node as read only' can edit it.

Downloads

Hierarchical Select Access

Hierarchical Select Access

This module prevents certain roles from accessing the enhanced hierarchical menu provided by the Hierarchical Select module in content types.

Provides a UI to manage roles and content types.

This module helps solve this issue: https://drupal.org/node/298611

After enabling the module, go to admin/config/content/hierarchical_select/access
and tick the checkboxes next to the roles that should not access the hierarchical menu in content types.

Downloads

Le Gate- A generalized age gate solution

Le Gate is a simple module that restricts user access to pages on a site, and then provides two mechanisms
by which users can then gain access. It was first developed as an "age gate" module to allow access to a site
only when an appropriate age is selected (>15yo for COPPA). But then we decided to make it more generic.

When a user tries to access a restricted page they are redirected to a configurable and themable page
(the "le-gate" page) that presents one of two ways to gain access. When access is gained a javascript cookie is set.

Downloads

Shield Pages

Shield Pages modules allows the administrator to secure any page in your website by password. You just need to go to configuration page of this module and add path, password. After that the added path will be password protected.

This module allow administrator to set global password for all shielded pages.This module allow administer to set multiple passwords for shielded page per path. This module provide bypass password protection of shielded pages permission also. All the shielded pages will be accessible by users having this permission.

Downloads

GeoIP Role

GeoIP Role allows to attach countries to roles.

GeoIP Role allows to dynamically grant roles to the current user according to his IP address location.
It depends on the GeoIP API module.

Currently, GeoIP Role allows to attach countries to roles, thus defining geographical zones.
When a user visits your site, he dynamically gain the role(s) attached to the country reported by his IP address.

GeoIP Role may be used with any other module like Nodeaccess that controls access based on user roles.

Downloads

OG Node Access

When you update the privacy settings of an Organic Group, you may need to rebuild the node access settings of the nodes assigned as posts to that group. Unfortunately the node access rebuild system focuses on rebuilding all nodes, instead of just those affected.

This module has forked the node rebuild system to allow developers to target one or more Organic Group's for node rebuild. It has the following features:

  • Automatically detect when group privacy changes as the result of the node edit form and directs users automatically to the batch edit screen.
  • Integration with Spaces allowing group administrators to rebuild node access for their group at need.
  • Developer API in the form of a og_node_access_needs_rebuild() function to add new groups for rebuild.
  • Plays nicely with general node access rebuild flag, allowing general node access to trump og-specific rebuild.

This is in response to #1101738: Repairing node access permissions without rebuilding all, thanks to @btopro for getting the ball rolling.

Status

This module is set for maintenance and bug fixes only and is unlikely to get much in the way of new features. Good, minimal feature patches are welcome. As we currently have no use for a D7 version of this module, we are open to requests to create and co-maintain a D7 branch.

Downloads

Simple Ready Workflow

Simple workflow module preview

This module adds a new "ready" publishing option on node bundles and fine-grained permissions on publishing options.
It gives you a simple worflow:

  • Ready not checked (draft)
  • Ready checked (ready to be published)
  • Published checked (and surely ready!)

If you need a more suitable and customised workflow, you better look at Worflow module: http://drupal.org/project/workflow

Downloads

Workbench Access Content Type

Extensible editorial access for the Workbench suite for granular access permissions by content types.

This module will add a new tab "Content Types" at the configuration page of Workbench Access, to provide permission by Section by Content Type.

This module was developed by Vardot for Georgetown University in Qatar.

Vardot

Downloads

Predelete

The predelete module hooks into the deletion process of nodes. By default it is not possible to react on a deleteion attempt before the deletion of a node. This is cured by providing the hook_predelete_node(). Other modules may implement the hook and add custom checks on the node that is about to be deleted.

The module ships with an API documentation and an example module that provides a single checkbox field. Nodes that contain the field could only be deleted if the checkbox is checked.

Downloads

Iron Curtain

Developed by Reload, sponsored by Scribo.

This module allows the site admins to restrict access to certain paths or the entire site, based on the visitor's IP address.

It allows users with a certain role to bypass the system, it allows a list of paths to bypass the system and it allows you to make a list of paths which can only be seen by whitelisted IPs, and another list which can not be accessed by blacklisted IPs.

Downloads

Session node access

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.

Downloads

Brain Forum Moderation

brain_forum_moderation.png

With Brain Forum Moderation you can add "Moderation" field to your
Brain Forum posts.
It creates an ajax link that opens a popup with variety of moderation options when clicked.

Development has just started so it will take some time before even the basic features are ready for production.
You can help by opening feature requests so i can figure out which features are actually needed.
These are some planned features:

Downloads

Ctools Compare ID

Settings form

The module provides a ctools plugins to provide access control by checking for equality ID.

Supported entities for check access:

  • Node
  • User

An example of using the module:

  • Deny the display of the page to a particular user, if you know its identifier.
  • Overriding a specific page.

Downloads

URL token

URL token is an API module to make token-based access control simple.

There are two main features:

  • Request a token
  • Check that a token is valid (usually via a URL)

You should only install this module if another module requires it. This module doesn't provide any functionality by itself, it provides features for other developers to use in their modules.

Downloads

Field ACL

This module will grant access to a node from a field. The field contains usernames.

This module requires the ACL Module.

This allows you to give users different access to every node.

This module is also compatible with nodechanges

Downloads

One-time File Download

This module allows you to provide single-use URLs to files stored in Drupal's private file-system.

Downloads

Pages