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.
A simple module that tracks downloads of files added through CCK/Fields by asking anonymous users to enter their email address. Returning anonymous users are tracked using a cookie. A tracking interface shows email address and user account information for tracked files downloaded on the site.
Why only have users enter their email address? Email addresses are a unique and easy way to identify users, and the barrier for entry is lower than actually registering for the site.
With this module you can lock fields in a webform so that those fields cannot be deleted or modified except by administrators with appropriate permissions. It was written to work in tandem with the Webform Default Fields module but is not dependent upon it. The idea is that if you create default fields for a webform, you may want to ensure consistency by preventing webform creators from modifying some or all of the default fields.
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.
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.
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.
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.
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.
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.
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.
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).
OG Workflow integrates the permission systems of Organic Groups (OG) and Workflow. Permissions for workflow state transitions can be granted based on OG group roles (see screenshot).
Use Version 1 for OG 1.x. There is no node access control for this version, but you can use Rules to bind state transitions e.g. to publish/unpublish actions.
Version 2 integrates with OG 2.x and is not compatible with OG 1.x. Additionally, it integrates with og_access (part of OG). That means that private entries in groups are respected and people cannot view them even if workflow would allow them (enable strict access control in OG settings).
Generates link for view, edit, or delete content without login.
Module maintains authorization key for every node and gives additional grants (view/edit/delete) to every user (anonymous too) who accesses page with correct key in URL. Module offers function node_authlink_get_url($node, $op = 'view') for generate absolute URL to selected operation (e.g. for e-mail notifications).
Authkeys are generated for every node (in configured content type) once for all operations. In content type form you can configure which operations to allow and authomatic expiration of keys.
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
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.
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.
Anti spam module by CleanTalk to protect your Drupal sites from spam bot registration and spam comments publications thru comment and contact forms.
Invisible antispam without CAPTCHA, questions, puzzles, counting animals, math and etc. Just install and forget.
CleanTalk is a SaaS spam protection service for Web-sites.
CleanTalk uses protection methods which are invisible for site visitors.
Using CleanTalk eliminates needs in CAPTCHA, questions and answers, and other methods of protection, complicating the exchange of information on the site.
Module is tested and ready to protect against spam bots for Webform.