603 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.

Drupal Firewall

Drupal Firewall

Module maintainer @podarok
Drupal Firewall was implemented due huge data importing into commerce, ubercart, feeds and other modules
The main idea - disabling redundant hooks, functions and other procedures when doing background tasks (mostly via cron or custom page callback)
For that we use hook_module_implements_alter

Module config page (sometimes You have to know this address 8) ) admin/config/dfw/config

Profile2 Privacy

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

Installation & Configuration

You must configure this module! Failing to configure this module will result in inaccessible user profiles. In order to protect user privacy, profiles created prior to enabling this module will have strict access control (i.e. be inaccessible), until the user updates the setting.

  1. Go to http://example.com/admin/modules and enable the Profile2 Privacy module.
  2. Go to http://example.com/admin/config/people/profile_privacy and add a profile privacy level.
  3. Give your privacy level a title and description. Both of these fields are displayed to profile owners to help them determine with privacy level to select.

Webform Invitation

Purpose: The Webform Invitation module allows you to restrict submissions to a webform by generating codes (which may then be distributed e.g. by email to participants).

Usage: Install module using the standard procedure. When viewing a webform, there are two new pages under "Webform".

Block permissions

This module provides additional permissions for finer grained access validation in managing blocks.

The following permissions are added:

  • An administer blocks per enabled theme.
    This enables granting a client access to managing the blocks without them beeing able to change the blocks on the admin theme.
  • Permissions per provider of block plugins.
    This enables granting a user permission to add certain types of blocks but not system block plugins.

This module is for Drupal 8.x only.

Restrict Page IP

Provides administrator to restrict/allow access to pages based on user IPs.

Features
--------
* IPs can be an individual IP or range of Ips.
* Page url can have wild cards like 'blog/*'
* Restricted user IPs will be denied showing
custom error message (can be modified on module's configuration page)

Note : User 1 has been skipped from these restrictions.

TAC Unpublished

The TAC Unpublished module is an extension module for Taxonomy Access Control (TAC). It allows TAC's grants to control unpublished nodes.

This module allows administrators to grant certain roles the Use Taxonomy Access Control for unpublished nodes permission. Users with this permission can access unpublished nodes according to TAC's taxonomy-based grants. Users without the permission are denied access for unpublished nodes.

Token Content Access

Token Content Access allows you to restrict access to individual nodes using URL tokens. In order to view protected nodes, users must provide a unique token via the URL. This allows nodes to be published and viewable to anonymous users (for instance with a special link from an email campaign) but not visible to the public at large. It also automatically hides any TCA-protected content from Views results.

Switch User

This module is no longer active. The Masquerade module does what this module does, only better, so go and download that instead.

The difference with Masquerade and my module is that mine displays the "switch" link along side the "edit" link for users, where as Masquerade has the option to masquerade as a user in the operations dropdown. Masquerade also logs the user-switching as well as giving you a switch-back link, so it is truly superior.

Frontpage

This module allows setting a node as frontpage for anonymous and authenticated users. Users can be allowed to set the frontpage by setting the appropriate permissions.

Once the module is enabled

  • two new links will appear at the end of the node body (Set as anonymous frontpage, and Set as authenticated frontpage) for any content type that has been enabled, and for the users with the right permission;
     
  • Two new node operations will appear at admin/content (Set as anonymous frontpage, and Set as authenticated frontpage) for any user with the right permission.
  • Only users with the edit frontpage permission, or the bypass node access permission can edit the node that as been set as authenticated (anonymous) frontpage.
     
  • Only users with the set frontpage permission, or the bypass node access permission can set the frontpage for the authenticated (anonymous) users.

 

Node access book

Gives content access permissions on a book child page if users have access to the root of the book, typically provided by another node access module. Checks view, update, and delete grant operations, and can pass those on to the referencing content, or trigger a different grant configuration according to settings(not yet).

This module is a spin-off from Node access node reference and it's functionality is very new - use with caution!

Manager access

Description

Module provide an additional functional for content managers:
1) Manager role
2) Manager menu with ability use this menu in "admin menu style"
3) Hide unnecessary fields on node add/edit forms.
4) Show add "content type" button on selected node type / view pages. (Contextual links style)

Requirements

Drupal 7.x

Installation

1. Copy the entire pager_for_content_type directory
the Drupal sites/all/modules directory.

2. Login as an administrator. Enable the module
in the "Administer" -> "Modules"

Settings

1. Go to "Configuration" -> "Manager Access"
2. "Manager access fields" - set checkboxes for fields and for roles. Selected fields will not show on add/edit form for user which have selected role.
3. "Manager links settings" - set checkboxes for content types and for views. On selected views and content types will be added additional contextual links for manager.
4. Go to "People" -> "Permissions" and select roles for "Use manager links" and "Access top manager menu"
5. Go to "People" and add manager role to your user

This project has been sponsored by:
Volcanoideas Drupal consulting and development.

Workbench Moderation Profile

Workbench Moderation Profile adds the ability to have multiple workflows, divided into profiles, based on the states and transitions defined by Workbench Moderation. These workflow profiles can then be applied to nodes based on criteria you determine, and an API is included to help with that process.

Content Language Access

Content Language Access Module restricts the access of only contents with language (except neutral language) that are equal of the actual Drupal language being accessed or others that were previous configured in the admin page.

This module helps when you have a content that needs to have access restriction by Drupal language.

Example

Node menu parent select

Small module that fixes the parent menu link select element on node forms, when using multiple modules that alter/restrict the available parents.

Automatic IP ban (Autoban)

Ban bots using rules

Autoban allows to automatize IP ban using watchdog table by the module rules. Need enable Database logging module (core). The module ban IP by cron (cron mode) or at every dblog event (force mode).

Rule module finds IP in watchlog table entries and inserts IP to banned IP table. By default, IP is inserted into blocked_ips table (admin/config/people/ip-blocking). After installing IP_ranges module you can ban IP range (aaa.bbb.ccc.0 - aaa.bbb.ccc.255).

Page Access

Page Access

This module will provide the option to give the View and Edit access for users and roles on each node pages.

Content Dependency

content dependency | entity dependency | node edit

Provides ability to view reversed referrals/references for content of entity reference & references - node_reference modules, etc.

Generally, this project enables content authors to see from any current content (entity) its dependent entities content.

Project overcome a major content control difficulty for content authors.

Provide content authors ability to track external content which refers to current content, without the need to check mass of external content to find out whether each external content refers to current content or not.

Content dependency main advantages:

  • Easily manage content dependencies - you can view/update for each content entity it's dependent entities from one places.
  • Backward Compatibility - You can install this module & start use it without need to perform any change in your content structure.

Block Country

This module helps to create country specific Blocks. It Add country setting to block and manages country specific display of block.

Block will be only visible for the selected countries. It detects and gets User's country from Ip2Country information and based on this it manages block visibility.

CONFIGURATION
To add country specific visibility to a block, Go to that block's configuration country settings is listed under block "Visibility settings"

User Comment

Overview

User Comment gives you more control over comment permissions. With this module your users can administer, approve, and delete comments on nodes they create without giving them full comment administration access. Permissions are on a per node type basis, so it's a great way to, e.g., allow users to manage comments on their own blogs.

Domain roles

Allows you to save user roles per domain. Allows a certain user to be just authenticated on one domain and admin on another etc.
To configure this module,

  1. Enable Module Domain Access.
  2. Navigate to 'admin/structure/domain/domain_roles'.
  3. Enter a comma-separated list of users to whom you want to assign roles.
  4. Select the checkbox corresponding to different roles in all domain or for particular domain.

Deep link

Sometimes you want to be able to give simple URL access to content that would not normally be available to a particular user (or perhaps someone not even registered with the site).

Deep link module allows the direct access to a specific item of content under certain circumstances and limitations. Such as one-off or time-limited deeplinks.

The deeplink module provides a framework for generating special URLs which can be inserted into emails that allow access to a content item or page, and tracks the uses of that link.

The controls that go with deeplink provide the means by which users are selected, one allows selection by user - so only users will receive the deeplink and only those users will be able to use it; and by email: this allows you to enter a set of email addresses that will be sent the deeplink URL. Obviously this one is more limited in that unregistered users can look at the content.

Other controls, for example to select by role, could be built.

Installation

1. Install module and the Controls module.
2. Enable.

Features

  • generating one-time or time limited login access for specified entity,

Requirements

http://drupal.org/project/controls

Similar modules

http://drupal.org/project/one_time_login (?)

Content Access Roles

Contentaccess Roles Settings

The Content Access Roles module gives node authors the ability to let users in selected roles to view nodes.

This module is great, if you want to show node teasers on the front page while restricting body access to authorized users.

Access to Term page by Role

Description

This module allows you to restrict access to term page based on user roles. It depends on the Drupal core taxonomy.module—just activate both modules and edit a term item as usual. There will be a new fieldset that allows you to restrict access by role or close term page for all roles.

If you're interested in helping with this or have problems with this module, please contact me or open an issue in the Term per role module issue tracker.

Installation

Installation is like with all normal drupal modules: extract the 'term_per_role' folder from the tar ball to the modules directory from your website (typically sites/all/modules).

Configuration

Just open to edit edit or create term and add seetings to new fieldset that allows you to restrict access by role or close term page for all roles.
In admin area(path is admin/config/content/term-per-role) you can change behavior if access is denied to page(show page 404 or 403).

Credits

This project has been sponsored by:
Volcanoideas Drupal consulting and development.

Where is this module used?

Domain Default Redirection

This small module provides a redirection feature instead of providing the default domain contents in the Domain Access suite.

In a nutshell, subdomain redirection handling will be shifted from your domain's DNS settings to your Drupal installation, redirecting all subdomains to the specified URL while still serving Drupal content to the subdomains set in Domain Access.

uc_cck_access

Ubercart compatible module.

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).

Pages