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.
Allows administrators to override the visibility of menu items. Normally, items which are inaccessible won't show up in the menu. Using this module, menu items can be set to always show up. Their contents will still be restricted.
Block upload - it's a simple module, which allow users to upload images/files into field without node edit page. You can add this block on node pages. Choose field you want to upload files and set permission. So, for example, users can add new photos into node without full node edit rights. You also can quickly add new files into node, avoid edit form.
Install module and go to Blocks management page, than find Block upload. On edit page choose file/image field you wish to use and save settings. Choose block position and here it is. Additionally set user permissions to allow uploads.
7.x-1.1 New features
Integration with Plupload integration module what makes available to use multiupload and drag&drop features.
To enable it, install Plupload integration according to it requirements. Than go to block upload config and tip use plupload option. This will switch single form to plupload widget.
The Agreement module allows the administrator to present a text-based agreement (think "Terms of Service") that users of a particular role must accept before they are allowed to access the site. The agreement is presented to users right after login, and must be accepted before the user can navigate to another page. Users will still be able to access the homepage (<front>) and /logout without accepting the agreement; all other pages will redirect the user to the agreement acceptance form.
Field Readonly displays non-accessible fields in edit forms as read-only items.
Modules like the essential Field Permissions allow to make fields non-accessible, aka private, by completely hiding them in edit forms even if user has the permission to view them. Field Readonly lets you display these fields back in edit forms, rendered the same way as in view mode.
The Access Control Kit (ACK) module provides a customizable system for controlling access to all kinds of things in a Drupal site. It gives site builders the flexibility to define access based on whatever conditions make sense for the site through an easy-to-understand UI.
Edit Limits adds certain limits to editing nodes and comments. This can set the number of times a node can be edit. This can also set a time frame for nodes to be edited, as well as a different time frame that comments can be edited.
Limits on nodes can be combined, so that a node can only be edit a set number of times or within the time frame.
This module allows integration between workbench moderation and organic groups. Organic group roles can be defined to be responsible to perform different transitions that will move content from the different stages.
A perfect use case for the usage of this module: a website with several groups that contains a content workflow process.
Users with "Content author" role in group "Finance" can create content that needs to be approved before being published to "Finance".
Only "Content editors" of group "Finance" can review and publish those nodes.
"Content authors" can create new revisions of content that is curently published. That content remains published till the new revision gets reviewed and published.
"Content authors" and "Content editors" of different groups will not have access to content that is under review in group "Finance".
This modules allows group managers to configure permissions that allow members with defined roles to move nodes in defined workflows configured using workbench moderation. Instead of configuring permissions to transition nodes to be published by normal roles, this module allows to do in a group context defining group roles that can publish nodes.
Organic Groups allows content itself to be groups, which isn't always what people want. It relies on an entity reference field to keep track of the ties between a group (node, term, ...) and its content (node, term, user, ...).
Part of the Debut features set, Debut Member provides member-related roles and member content type.
Like all Debut features, Debut Member can be integrated either as a stand-alone feature to quickly add blog functionality to any Drupal site or as part of a Drupal distribution. Debut Member is used in the Open Outreach Drupal distribution aimed at nonprofits.
You have two options for installing Debut Member:
Debut Member is used in the Open Outreach Drupal distribution aimed at nonprofits, so you can install it as part of Open Outreach.
Install manually along with the dependencies listed below.
Roles: member and membership manager.
A content type, Member page, with access restricted to members and membership managers.
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.
This module extends the content access module to put the view (any/own) [TYPE] to the drupal permissions form. So a user settings the access permissions doesn't have to switch between two forms and he doesn't need access to change content type settings.
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.