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


A model of how token works

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 Demo Screenshot

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.


Profile 2

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!


Comparison to user account fields

As described in the documentation Drupal 7 allows adding fields to user account pages - what serves as simple way for building user profiles. The main differences between that and profile2 are:

  • With profile2 user account settings and user profiles are conceptually different things, e.g. with the "Profile pages" module enabled users get two separate menu links "My account" and "My profile".
  • Profile2 allows for creating multiple profile types, which may be assigned to roles via permissions (e.g. a general profile + a customer profile)
  • Profile2 supports private profile fields, which are only shown to the user owning the profile and to administrators.

Relationship to content profile



Twitter module in action


This module provides API integration with the Twitter microblogging service. Out of the box, it allows users to:


Webform Rules

This module adds rules integration on webforms.


Inline Conditions

This module allows conditions to be defined on the entity add / edit form, and
 those conditions are later mapped to rules conditions when the rule is generated.

Inline Conditions are specially defined (hook_inline_condition_info()) and
 consist of a configure callback (provides a user-facing form) and a build
callback (adds the actual condition to the rule).

Integration consists of creating a field of the "inline_conditions" type on the
 entity, and later calling inline_conditions_build() from the implementation 
of hook_default_rules_configuration().


Content Profile

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.


Conditional Rules

Provides inline conditional branching in Rules configuration.


User Points

My points page of a user

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.

Userpoints is included in the Drupal Commons distribution.


Entity Rules

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.

This module allows users you don't have access to the Rules UI to select Rules to be triggered for bundles that they can manage. This can be useful for module such as Entityforms, Entity Registration, and Entity Construction Kit.

Video Intro

For example usage see the Entity Rules Node Limits sandbox project. This creates 4 Form Access rules.

Want to help?


Cache Actions

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:

  • Panels 3
  • Views 2 and 3. The views 2 support is the best tested currently, but everything seems fine
    with views 3 as well.

Version 2

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
  • Clearing The cache of specific mini panel panes
  • Unit tests


Views Rules

Provides Views directly as Rules actions and loops to seamlessly use view result data.


User Stats

Provides commonly requested user statistics for themers, IP address tracking and Views integration. Statistics are:

  1. days registered;
  2. join date;
  3. days since last login;
  4. days since last post;
  5. post count;
  6. login count;
  7. user online/offline;
  8. IP address;

This module was developed for The Webmaster Forums (who have moved to Drupal from vBulletin -- yes, we do like Drupal's forum!)


Custom Publishing Options

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.


Commerce Cart Expiration

This module provides a time-based cart expiration feature for Drupal Commerce.



Commerce Rules Extra

This project aims to be a library of Rules events, conditions and actions for Drupal Commerce. Actively maintained and tested on a large eCommerce site. We are always seeking collaboration with other Rules based DC modules.


Mail Logger

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.


Field formatter conditions

Field formatter conditions screenshot

Adds conditions to field formatters. Configuration happens on the "Manage Display" screens of every entity type on a per field basis when clicking on the cogwheel on the right.


Simple conditions and actions

  • Hide source field when target field is empty.
  • Hide source field when target field is not empty.
  • Hide source field when current user has specific roles.
  • Hide source field on specific pages.
  • Hide source field when target field contains a specific string.
  • Hide source field when target field doesn't contain a specific string.
  • Hide link field if title is empty.
  • Hide date field if from/to has expired.

Rules actions

  • Hide a field.
  • Change image style.

Rules should always be a 'A field is rendered' event before they can be selected in the conditions dropdown on the "Manage Display" screens per field.


Field formatter settings

Comparison with Conditional Fields

  • CF uses a complete separate interface.


Web service client


This module provides an interface to consume external web services. It focuses on integrating web service operations as Rules actions, but can also be used as data provider for other modules.


Facebook Autopost

Facebook Autopost: Rules integration

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


Path Rules

Path Rules implements Rules conditions for checking the URL against a given string for triggering actions.


Setup a rule with the event 'Drupal is initializing', add 'Check path' condition with path 'project' and Operator 'Begins with'.

The rule will be triggered by:


Voting Rules

Public Domain vote button

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.


Menu Rules

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.


Here are the rules as of now.


Boolean Field

Provides a "boolean" field type with an additional state of "not set" in addition to the usual "true/false" or "on/off." A separate display string can be defined for each state. For example, if the field represents the status of a cron job, the three display strings might be:
- Cron job completed without errors
- Cron job completed with errors
- Cron job has not been run.

The corresponding default storage values are 1, 0, and -1.

The field type is integrated with the Rules module.


Node Limit Number

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.

Version 2.x

  • Depends on Rules
  • Complete rewrite of the original module
  • Can limit the creation of nodes and comments
  • Conditions for the limits are anything that you put into a condition for a rule
  • Integrates with Organic Groups

Version 1.x

  • Port of the Drupal 5 version
  • Can only limit the creation of nodes
  • Conditions are only by role

Bug Reports & Support Requests

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.