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.
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.
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.
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
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).
Provides administrator to restrict/allow access to pages based on user IPs.
* 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.
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.
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.
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.
This module changes your image gallery administration page to allow you to set image galleries private. You can control what user roles can view, edit, delete and post to each gallery. You can also give each gallery a list of users who have administrative access on that gallery (AKA moderators).
Image galleries are provided by the Image Gallery module inside the Image module. Image Gallery Access also requires the ACL module in order to function.
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.
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.
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.
This module adds new field formatters for entityreference which check access before displaying rendered entities. Views has access filters such as 'published', but entityreference rendered entity formatter only checks entity_access() for the current user.
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.
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 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).
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).
This project has been sponsored by: Volcanoideas Drupal consulting and development.
UC Node Access lets you attach Node access features to products in your Ubercart store. These features allow customers who purchase the product to receive view access to nodes on your site either indefinitely or for a limited time based on the feature's settings. UC Node Access does not handle access grants itself but rather depends on other modules to define handlers that integrate UC Node Access with the various node access modules developed for Drupal.
Currently integrated node access modules include:
ACL + Content Access - adds the customer's user account to the ACL defined by Content Access and adds expiration information beside the names in the Grant view access fieldset of the Access control tab for nodes governed by Content Access.
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.
This module defines context and access rules plugins for CTools (and Panels) based upon values of HTTP request header elements. The following headers are exposed into context and can be used as access rules parameters: