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.
Tokens are small bits of text that can be placed into larger documents via simple placeholders, like %site-name or [user]. The Token module provides a central API for modules to use these tokens, and expose their own token values.
Note that Token module doesn't provide any visible functions to the user on its own, it just provides token handling services for other modules.
Flag is a flexible flagging system that is completely customizable by the administrator. Using this module, the site administrator can provide any number of flags for nodes, comments, users, and any other type of entity. Some possibilities include bookmarks, marking important, friends, or flag as offensive. With extensive views integration, you can create custom lists of popular content or keep tabs on important content.
Flags may be per-user, meaning that each user can mark an item individually, or global, meaning that the item is either marked or it is not marked, and any user who changes that changes it for everyone.
In this way, additional flags (similar to published and sticky) can be put on nodes, or other items, and dealt with by the system however the administration likes.
Designed to be the successor of the core profile module, which is deprecated for Drupal 7. In contrast to the deprecated module this module provides a new, fieldable 'profile' entity - leverage the power of fields!
This module builds user profiles as content (aka nodes), which opens the opportunity to use all the powerful modules for content for user profiles too, e.g. the Content Construction Kit (CCK). It's intended to be simple and useful, but extensible by further modules.
Content profiles can be restricted to certain roles; the module also supports separate content profiles for different roles.
This module provides an API for users to gain or lose points for performing certain actions on your site.
In conjunction with other modules, such as the Userpoints Nodes and Comments users can accumulate points for actions such as posting nodes, commenting or moderation duties.
Use one of the many contributed modules to extend the functionality of the module to include point accumulation on page views or votes, upgrade roles based on point balance, or purchase goods from your store.
This module is useful in providing an incentive for users to participate in the site, and be more active.
Cache actions provides rules actions for clearing drupal caches.
It currently provides actions for:
Clearing Drupal cache bins
Clearing CSS/JS cache
Clearing The cache of specific views
Clearing The cache of specific panel pages
Clearing The cache of specific mini panels
Cache actions only depends on the rules module. If you don't have views or panels, you only get the option of clearing the drupal cache bins and the CSS/JS cache. When views or panels are present, you get actions for clearing the cache of specific views and panels as well.
This module is compatible with:
Views 2 and 3. The views 2 support is the best tested currently, but everything seems fine
with views 3 as well.
The new version of cache actions offers a lot of new features:
Clearing The cache of more than one view at a time
Clearing The cache of specific panel page variants
Clearing The cache of specific panel page panes
Clearing The cache of specific mini panel variants
This module allows you to create custom publishing options for nodes. It allows you to add to the default options of Publish, Promote to Front Page, and Sticky. It also ingrates with views to allow you add as a field, sort and filter by, your custom options.
It now allows each of the different options to be shown only on selected node types, as well as integration with Rules, Actions, and Features. Custom Publishing Options also have granular permissions per role, per option.
Hansel (named after Hansel and Gretel) provides custom breadcrumbs which are build by user defined rules. These rules are independent from the menu system. Rules can have logic switches and can add links to the breadcrumbs.
Logs all outgoing mail from your site that uses proper Drupal APIs.
Any user with "access mail logger" permission will be able to read logs of outgoing mail from any user to any recipient, including new user welcome emails, password resets, triggered actions, Rules-based actions, and more.
Content Complete is a CCK extension module that allows to tag CCK fields needed for completion (CCK Complete). The module checks the tagged fields against the content provided for those content types, and computes a complete percentage that can be shown to the user.
The complete percentage can be shown to the user in the form of a block, or using the views integration available since version 1.2.
Limit the amount of nodes or comments your users create over a given time period. This module has been rewritten to integrate with Rules. Instead of going to a page to assign limits you now just need to create rules. A default rule has been provided as an example.
When creating your rules there are now many hundreds of ways to implement your limits. Limits can be applied to roles, users, dates, or anything that can be accessed using PHP.
Please include all relevant information when posting an issue to the queue. This would include your exported rule, a detailed description of what you are trying to do, and any other pertinent information. The more information you give me the quicker and easier I will be able to help you.
Voting Rules provides Rules integration for the VotingAPI module.
Administrators can configure actions to occur when a user submits a vote, when a user deletes a vote, and when the results of a vote are calculated. Currently, Voting Rules supports votes on nodes, users, and comments.
Supported conditions include acting on the total number of votes, average vote, the sum total of all votes, as well as any conditions provided by other modules on the node, user, or comment that is being voted on.
Entity Rules provides a page for selecting and creating Rules components that will be executed when different operations happen to an Entity of a particular bundle. This provides an alternative method of triggering Rules. Instead of adding entity related events to Reaction Rules you are able to select which Rules will fire from the bundle management page.
Currently the operations supported are create, update, delete, validation and form access. You are also able to pass different arguments to the Rules per bundle.
Most PDF modules generate PDFs from scratch; FillPDF is not one of those modules. Instead, it lets you fill in existing editable PDFs with data from your Drupal site. Editable PDFs are those forms that let you type into them. Read more.
Facebook autopost allows you to configure your site to automatically post to a user's Timeline (configuring the privacy) or to a Facebook Page without human intervention. No tricky configuration needed.
Watch video demonstration here. There is also a Spanish version aquí.
Menu Rules provides Rules that are related to menu items. This project started out of the need for a D7 replacement for Automenu. I realized that achieving the same results through Rules would be both quicker and more generic than writing a module specifically for that use. Menu Rules simply aims to integrate the menu system with Rules in a comprehensive way.
This module adds a new node option Premium content along with core publishing options (Published, Promoted to front page, Sticky at top of lists).
When a node is published as premium content, only users with proper privileges may view the full content of the node.
Non-premium users can still access premium nodes but only get the content rendered in teaser context, even when trying to view the full content. An additional message informs them that the content is available to premium users only.