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

URL alias restriction

Drupal is quite talkative in terms of showing off it's content. Often it makes content accessible which we actually don't want to show. That happens for instance very easily, if you're using nodes as content containers only - never really wanting to show the actual node pages of these containers.

Thanks to taxonomy node and similiar listings + some SEO javascript "callling home" often these unstyled content containers land on public search indexes as soon as an Administrator has an accidental look at these listing or node pages.

Workflow Content Permissions

This module allows the site administrators to control the permissions to edit or view fields of a node that participates in a Workflow for each state.

It's based on the Content Permissions that comes with CCK.

Depends on CCK and Workflow

Unpublished 404

Unpublished 404 is a simple module that emits a 404 (Not Found) error when a user tries to access an unpublished node instead of the default behavior of emitting a 403 (Access Denied).

Path Access plugin for CTools

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

Field Paywall

Field Paywall allows developers to replace fields on entities with a message depending on user permissions. It's useful for giving visitors teasers to content before advising them to sign up to see more.

Walkthrough video

A walkthrough video is available at http://youtu.be/a-Y8tiHuvaQ with a full demonstration of how to use field_paywall and how to override field_paywall templates.

Webform Per Email

Attaching to a webform

Introduction:

This module implements a permit based access system to allow anonymous users submit a Webform only if they display a valid one-time access permit.

Publication Agreement

Publication Agreement:  A Terms and Conditions example page.

Agreement prior to publication.

This simple module allows you to present a text-based agreement that users of a particular role must accept before they are allowed to access for adding a new node.

Custom Listing Pages

The Custom Listing Pages module provides the ability to create custom pages with data from existing content types.
- Display data from an existing content type with various options including:
- View Mode to display.
- Filter by one or more taxonomy vocabularies linked to the content type selected.
- Filter further by the tags for each selected taxonomy vocabularies.
- Sort by (title, last updated date, created date)
- Sort order (ascending, descending)
- Entries to display per page (pagination)

This module differs from Views as one of its main goals is to allow a content editor to publish listings of content without requiring administrative rights to the Views module. In a larger environment, you may need site builders or delegated site section owners, to create a listing of selected content. Using this module, this can be done and it's as simple as "Create new content" of type Custom Listing .. select the content type "profiles" , filter the output by selecting any assigned taxonomy terms and then select one of the pre-defined view modes. The Site Administrators will have created standard entity view modes for the selected content type, which can be themed with the necessary fields.

Example Use:

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.

Menu Node Edit

My section editing screen

Allows node editing access based on menu relationships.

The Menu Node Edit module allows the site's menu system to be used as the sole organizing principle. It does so by allowing specific menu items to be defined as 'sections' of a Drupal web site. Individual users can then be assigned as editors of one or more sections.

Section editors are then granted access to edit all nodes that fall within a specified menu hierarchy.

This structure means that, for small web sites, the menu system can be used as the sole ordering principle, removing the need for taxonomy or group-based editing controls.

Drupal 7

For Drupal 7, this module is being replaced by Workbench Access. An upgrade path will be provided.

Dependencies

Use of the module requires that you download and install the Menu Node API.

Menu Node Edit and Node Access

The Menu Node Edit module is deliberately not a Drupal node access module. It does not provide any access controls for the viewing or deleting of content.

Node Gallery Access

Node Gallery Access node edit settings

Node Gallery Access is a module that adds access control to Node Gallery.

Node Gallery Access allows a gallery owner to specify a gallery as one of three different types:

WireDocs

If you want to share and work with your documents online Google Docs, Zoho, iNetWord, Office 365 or Sharepoint are most likely to be - depending on how deep you can dig into your pocket - the solutions of choice. Especially, a large legacy of documents in proprietary formats, such as MS Word or Excel, may discourage from moving to an online editor. Additionnally, legal issues might arise if confidential files are hosted by a third party service provider.

WireDocs is a lightweight remote file editing tool. It takes the best of both worlds: Drupal as a CMS being responsible for hosting files and applications on a operating system (OS) doing the editing part. The approach automatizes a manual process: a file is downloaded, edited by a local editor and uploaded to its original remote location again. WireDocs makes this procedure completely transparent from a user perspective. The user only watches the application opening the demanded file and uploads are processed in the background after the file has been saved. WireDocs integrates with Drupal's content structure, namely the Field API, and currently supports file and image fields.

Client requirements

As a Java applet bridges the gap between Drupal and the OS the client must fulfill some prerequisites:

    jQuery View Ticker

    Introduction:
    -------------------
    This module provides functionality to animating a simple news ticker.

    Requirements:
    ------------------
    This module requires the following modules:
    * None

    Installation:
    ------------

    * Install as you would normally install a contributed Drupal module. See:
    https://www.drupal.org/docs/8/extending-drupal-8/installing-modules
    for further information.

    Advanced User Registration and Management

    Customer Registration Service

    Note: There is no active development on this module, use LoginRadius Customer Identity and Access management module instead.

    User Registration made simple for your Drupal Website! Let users register via email registration or social login as per their choice and manage their profile with simple LoginRadius Dashboard!

    This plugin requires Paid Subscription of LoginRadius service..

    Delete Homepage Permission

    Summary

    This module adds a permission which can be used to allow or disallow certain roles to delete the homepage node. This is useful when some roles such as content administrators need to be able to delete nodes, but you want to prevent them from deleting the homepage node.

    Node Translation Access

    Node translation access module allows to control access to nodes for selected languages

    When using the entity translation module for node translation, all the available languages will inherit source language. In this case, node will be visible on all available languages no matter whether it has translation or not. Using entity translation module you can deny access to nodes of selected language. You can deny access to languages per node. Users will see standard access denied page.

    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.

    Moderation Dropbutton

    Backport of Drupal 8 submit button displayed as dropbutton for changing publications states of node.

    TAC Redirect 403

    TAC Redirect 403 extends the Taxonomy Access Control module by allowing you to specify a redirect URL for each taxonomy term. When a site visitor navigates to a content page that is restricted by a taxonomy access control rule, instead of Drupal's standard 403 (Access Denied) page being displayed, the visitor is redirected to the URL entered for the restricting term. This can be used to send people to custom "upsell" pages.

    For example, if your site has the taxonomy terms Basic and Premium, and these are used to designate content as only available to members at the corresponding membership tier, this module lets you redirect visitors attempting to access restricted content to a signup form for purchasing the necessary membership level.

    Dependencies

    IP Path Access

    Drupal Contributed Module IP Path Access

    IP Path Access is an access control module which allows an administrator to set a path and IP (or IP range) and prevent all users from accessing the path that are not accessing from the set IP address (or IP range).

    In other words, the module is intended to permit access to the path and IP set, and deny for all others.

    There are permissions available to specify which roles can add and delete IP settings, as well as user roles who can bypass the IP blocking.

    Multiple IP and path pairs can be set, as long as they do not exactly match.

    Review Token

    Review Token provides a tokenised URL for bypassing access restrictions on unpublished content.

    It can be used to provide per-node access for unpublished content to users without logins, though a specially crafted URL.

    Currently incompatible with modules which provide workflowed versioning, as the module will load the current published content, rather than a specific draft.

    Credits

    This module was originally created by Boztek.

    CTools Token Access

    Build Status

    Drupal module to restrict access based on token presence. You can even set up a token that expires after a certain time or expires after a selected number of hits.

    Use this module when you want to easily share restricted content with one click.

    This module provides:

    VideoWhisper Webcam Plugins

    This module is unsupported due to a security issue the maintainer didn’t fix. See SA-CONTRIB-2014-061 - VideoWhisper Webcam Plugins - Cross Site Scripting (XSS) - Unsupported for details.
    If you want to use this module, your options are:
    • Choose another, actively maintained module instead

    Entity bundle Redirect

    This module allows to create 301 redirections for unused entity paths, by bundle and language.

    For example, if you have some content type, and you don't want people to visit it's corresponding "node/%node" page (because that content type is not a page-like content type, it's just an object-like content type that must remain hidden).

    Another useful case, is when you desire to redirect Taxonomy term page to an existing View page, with a given exposed filter selected ($_GET parameter).

    Node access product

    Node Access Product for e-Commerce and Ubercart
    This module is unsupported due to a security issue the maintainer didn’t fix. See SA-CONTRIB-2015-045 - Node Access Product - Cross Site Scripting (XSS) - Unsupported for details.

    If you want to use this module, your options are:

    Provides 'Node access' settings for product nodes, whereby users who purchase the product are granted view access to content, which can be predefined either by taxonomy, by node, or by Views.

    Pages