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

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

Downloads

Node Access Keys

Overview

Node Access Keys helps to grant users temporary view permissions to selected content types on a per user role basis. You can have multiple Access Keys for different content types and user roles.

Downloads

Webform authorization code

The webform module provides ways to limit access to the webform based on user roles, a maximum number of submissions and more. If you want to limit access to a webform but still want it to be accessible for anonymous users, the webform authorization code module is right for you.

In the webform configuration you can set a pass phrase which is then used to protect access to the webform.

When a visitor opens the webform, the form and body content will be replaced by a pass phrase form. If the proper pass phrase is entered access will be granted to the full webform.

Downloads

Taxonomy access user

At first sight, you may think it's just another fork of already available module on drupal.org like taxonomy_access or tac_lite. First one is a taxonomy control access based on roles, second one is a taxonomy control access based on users. But both of those modules miss the - according to me essential - inheritance notion :
if you have access to one term, you don't automatically have access to the children nodes. My module does take care about inheritance and this way permit a powerfull user access control.

Downloads

Role indicators

Provides markup to indicate user roles and roles that can access restricted content.

Downloads

GeoIP Country

If you would like to restrict your content to only show in a certain country, use this module.

It depends on the location module to provide a list of countries, and geoip api module to determine the country a user is in.

Downloads

Privacy Per User

Privacy Per User provides a simple framework to enable privacy settings per user, similar to the privacy settings on a site like Facebook. Those settings may be used to check access for display of entire pages, elements of a page (such as in a theme), or as an argument validator in a View. This allows individual users to control access to things such as their profile, specific elements of their profile, or lists of content they may have made, e.g. flagged nodes. It offers a flexible API to allow additional privacy states to be added (e.g. friends only) and an exportable set of privacy types.

Downloads

YouTube Video Accessibility Controls

This module integrate YouTube Video Player Accessible Controls library which add buttons to control YouTube videos, this module requires ytp.js library click here to download the library.

This module depends on the following modules :

Downloads

AUL(Access User Lists)

AUL module contains API and UI for node access system. AUL module can be useful in your project when content access logic is not simple.

AUL(Access User Lists) is very similar to the ACL(Access Control Lists). The difference that AUL creates access per user and adds nodes to it(ACL works vice versa. It creates grand per node and adds users).

Downloads

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

Downloads

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.

Downloads

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

Downloads

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:

Downloads

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.

Downloads

Ubercart Order Access

Order Access settings page

Overview
This module allow administrators of an ubercart store to allow access to view / edit / delete / change status of orders only to certain roles and based on current order status.

Features

  • View orders by status and role.
  • (This feature replace 'view all orders' from Ubercart with view orders by status. For example you can now select for "role1" to view only New orders but not Completed ones. Also the user can search only orders that he has view access. Be careful that when you have 'view all orders' selected for that role this function is disabled and the user can see all the orders no matter of order's state.)

  • Edit order by role and status.
  • Delete order by role and status.
  • Change orders status by role and current order status.

Description
This is useful when you are running a store, powered by Ubercart and you have certain users that handle the orders. For example if a group "shipping" only has to put orders in "Processing" or "Shipped" but NOT in "Complete" or "Payment Received" this module allow you to achieve this goal.

Downloads

Encrypted Text

-- SUMMARY --

Encrypted Text provides the ability to store encrypted text field values.

For a full description of the module, visit the project page:
http://drupal.org/project/encrypted_text

To submit bug reports and feature suggestions, or to track changes:
http://drupal.org/project/issues/encrypted_text

-- REQUIREMENTS --

* Encrypt: http://drupal.org/project/encrypt

Downloads

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.

Downloads

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

  Domains:
    www.example.com (EN_US)
    www.example.com.br (PT_BR)

  Contents:
    node/20 (EN_US)
    node/21 (PT_BR)
    node/22 (Language Neutral)

Downloads

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?

Downloads

Domain Restrict Publishing

Synopsis

Domain Restrict Publishing is a helper module building on top of the excellent Domain Access module suite.

The module enables site administrators to restrict the domains a user can publish to, based on their assigned domains.

The module was designed to work with the "Set domain access status for all content" and allows content to be promoted to other domains while keeping control over which domain editors can edit it.

Downloads

Chinese Captcha - 中文验证码模块

Chinese Captcha

Chinese Captcha module, provided validation way by input a Chinese characters, this module is mainly developed for Chinese user , aim to prevent spam attack from robot,

I will be keep actively develop for this module, and I will add more functions, such as Ajax refresh feature, stay tuned!

If you have good suggestions or advice can also create a issue, let me know, enjoy!

中文验证码模块,是一种通过要求输入中文汉字的验证码,这个模块主要是为中文网站用户开发,目的是为了帮大家防止机器人垃圾信息的攻击。

我将一直积极开发并维护此模块,后续也将会增加更多功能,比如Ajax刷新等功能,敬请期待!

另外,强大的模块,需要您的参与!如果你在使用该模块后,有什么好的建议或者意见,欢迎在本模块页创建一个issue,让我知道,好了,享受它吧!

Downloads

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

Downloads

Domain Workflow Bridge Module

This module provides a bridge between Domain module and Workflow module. It makes it possible to have a multisite setup with Domain module and also maintain a consistent and working publication workflow.

Alternatives?

Downloads

Workbench State Access

This module works with workbench module
It will give you the ability to set the access for viewing/editing revisions based on the revision current state

For example, You can block the editor from viewing or editing the content after changing the state from draft to "needs review".

This module is sponsored and developed by Vardot.

Vardot

Downloads

Pages