670 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 Extra

The module enhances the feature of other great contributes modules.
Current enhanced modules are:
- Computed Field, Computed Field Tools
- Field Query
- Views Summarize
- Visitors

The list will be continued.
Mostly are tiny fixes so I can't move it to separate single module.

Once an extra module's fixes is merged to official module, this extra module will be removed out. Please let me know your request if you're one of the author of the module.

Access Private

This module allow accessing private nodes with a direct link.

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.

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

Domain SSL

This module adds support for mixed use of SSL and non-SSL (http and https protocols) for the 6.x branch of Domain Access.

Currently, Domain Access allows you to specify per domain whether to use http or https, and if a domain source is configured, URLs throughout that site (including form actions and so forth) use that protocol. However, if your site mixes use of both protocols (say, with SSL to protect the user login page, admin pages, or authenticated sessions in general), Domain Access does not support that configuration.

For background information, see the original issue: #758714: Allow both http and https for a given domain?

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

Content Paywall

Sponsored by CoLab Cooperative.

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.

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:

Restricted Area

Restricted Area

If you want to secure some specific entities (nodes/term/assets/etc) or specific pages (still in development), you really need this module.

It allows you setup login and password, in a simple way, for each important page.

All password stored as hashes, so there are no security issues related to third-party access to the database.


DrupalJedi Logo

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.

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.

Website shutdown

This module allows you to shut down/close a website.

All requests handled by Drupal will be redirected to a specified page, unless it is initiated by a user who has adequate permission to navigate through the site.

Access by entity

Access by entity module is a very simple way to manage permissions (view/edit/delete) by entity (content).

You can restrict access view/edit/delete permission for each content.

Notice :

  • The global administrator (user with id "1") will bypass all access checks.
  • "Authenticated user" role is ignored if the user has another role.

Example Use Cases

  • Publish and edit articles in groups with defined roles.
  • Premium content areas for specific user roles.

REQUIREMENTS

No requirements.

Email downloadable

Description

Super simple module that does 3 things:

  1. Provides a configurable “Download this node” link.
  2. Sends an email with a link to the download using a unique code.
  3. If the code is valid takes you to the download.

What a download is it’s up to you. The module provides a basic edwd-node.tpl.php you can override it in your theme or your module to customize it.

API Key manager

Interface for creating an API Key relation between a user and authentication key & secret

A basic approach to handling API keys, implemented to be used together with REST.

Using 4 different headers and a HMAC based approach to authenticate users, all POST, PATCH, DELETE, PUT requests can be authenticated – I have not attempted to do this using GET requests as those mostly have a tendency to be broken.

Notice that even though this is API Key based do not mean that the /session/token can be omitted.

The Loch Ness Module

This is a module that will allow for locking of editing of nodes and things. If you need advanced features please take a look at Content Locking. This module is designed with simplicity in mind. All locks are ephemeral and they are stored in the cache table.

Entity Reference Guards

Entity Reference Guards help you safely protect or clean up your entity references, based on actions performed on either entity (the referee or referent). It is based on Django's ForeignKey's on_delete behavior.

File Download Form

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.

Default Node Gallery

Add-on for the Node Gallery module that creates and maintains default gallery for every user.
The main goal of the module is to make image sorting easy, optional task, and to streamline the uploading process.

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.

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.

Two Factor Authentication

Synopsis

TFA login is 2 factor authentication module used to introduce second factor of authentication to default drupal login with help of miniorange auth API.

List of second factor authentication :

  1. Login with QR Code Scan
  2. Softtoken
  3. OTP on mail

Note : It requires miniorange authentication APP

Requirements

This module requires following modules as dependencies-

Email Captcha

Spambots become smarter and smarter, so usual ways like javascript base protection might not be enough to fight against email mining robots.

This module protects your email fields with captcha. It provides a field formatter that shows a simple View email address link instead of pure email address. When clicking on it, a modal dialog box shows up with a captcha protected form. The successful form submission reveals the email address within the modal.

Theme permission

This module extend theme permission.
Allow edit theme for specific role.

How to use ?

  1. Activate module
  2. Go to admin/people/permissions and select theme permission for specific role

Pages