4,620 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.

Annotate (Pro Drupal Development Ch. 1)

When looking through the pages of a Drupal website, users may comment on content if the administrator has enabled the commend module. But what about making an annotation (a type of note that only the user can see) to a web page? This might be sueful for confidentially reviewing content.

Demo sandbox myveryown

Demo sandbox

UC Allies Postcoder


Module integrates Allies postcode lookup services (UK only) with Ubercart.

Allies postcoder

postcoder.com offer postcode lookup. The developers and maintainers of this module are not affiliate with Allies in any way.


The module currently only interacts with Ubercart, however further builds will support site registration and general drupal usage.


This module was motivated by a lack of a non-developer user-friendly charting
solution amongst contrib modules when I needed one for a project.

This module makes it possible for users to create nodes that display various kinds of
charts. It also creates a configurable block that displays a chart.

It extends the Charts and Graphs (charts_graphs) module, therefore that module
must be set up correctly before you can use this one successfully. i.e. It
depends on charts_graphs module and its dependencies.


Matador is a different way of creating content for your site. It allows you to preview your content as your build it. In it's current state matador allows you to build content with list, paragraphs, pictures, files, and dividers.

After enabling the module, enable a content type to use matador by editing the content type.

Revisioning Scheduler

The Revisioning Scheduler is a simple, light weight module which extends the Revisioning and allows users to set a date and time for publishing and reverting nodes. When a user clicks Publish or Revert, a new form is displayed prompting the user to enter date and time details for when they want the node to be published or reverted to.

Depends on: Revisioning module

Note: This module is now a submodule of Revisioning 3.x in Drupal 6 and 7

Nodequeue Block

Nodequeue block module seeks to take every nodequeue and make it's drag/drop reordering administration interface available as a block.


This module checks content title field uniqueness via AJAX request. This module is based on http://data.agaric.com/node/365.

Demo sandbox module

This is a demo module for my website

Drupal Guestbook Views

DGBV use in frontend


Drupal Guestbook Views (DGBV) provides Views module integration
for the Drupal Guestbook (DGB) module.

One of the main objectives of DGBV is to provide a way of creation of differentiated UI's for the administration of guestbooks.


NZ Fuel Saver

This is a module that pulls car fuel ratings from the New Zealand Govt website.

This module has also been built for WordPress and Codeigniter

Webform Signup


The Webform 3.x module allows you to assign webforms to any Drupal content type that you want to have signups.
This module allows you to create an (unpublished) webform node as a signup form template
That webform's form components will be made available to each node of the content type you indicated as needing to have signup functionality.

You'll be able to select multiple content types that serve as "events" and can have a webform serve as signup form.


Workflow as a D7-field using rules.module for the "heavy lifting".

For an introduction on what this module does please check out the screencast and blog post. There is also a sample feature, and an install profile.


Version Agent enables you to compare revisions, with assistance of the GehsiFilter module, that have occurred in each of your Cerner or SQL environments – providing a powerful side-by-side color-coded interface to easily see what had changed. Version Agent can also provide a list of programs that are not in sync between your environments - making sure your testing and development starts on the right foot!

OG Forum Resurrection

OG Forum fixes for SA-CONTRIB-2011-004

Note: due to lack of time, I'm looking for a new-maintainer for this module.

Nodequeue TOC

This module will allow a nodequeue's table of contents to be displayed in other places besides within the block it provides. This filter will replace the shortcode [TOC] with the table of contents of the nodequeue that the current node belongs to. This filter will also replace [TOC-Name of Nodequeue] with the TOC of the particular nodqueue named within the shortcode.

Node Block Auto

Node Block Auto is an extension of the excellent Node Block module, which allows developers to specify content types that are automatically provided as blocks. Node Block Auto takes this a step further, and forces all nodeblocks into a region based on content type. This makes integration with blockreference much nicer, since available blocks can be restricted to certain content types by selecting their region in the blockreference field setup.


Polls aggregates core poll api into single content type to achieve polls forms

Test sandbox module

This is demo sandbox module for our screencast.

Feeds GIT Fetcher

This project is a Feeds plugin that fetches a GIT repository and clones it to the local disk. Once a GIT project has been cloned locally, you can then access the contents of that repository in the same way you'd make use of a local file.

URL IDs and Lazy URL ID Reference

The URL ID module provides a field that gives an entity a 'global' ID, based on the domain name, entity name and entity id (such as http://example.com/node/1).
The idea is that remote entities can be downloaded, inheriting the remote URL ID – a node could have the URL ID 'http://example2.com/node/123'.

The Lazy URL ID Reference module provides a lazy-loading reference field, utilizing URL IDs. The idea is to refer to a URL ID such as 'http://example2.com/node/123'. If there is a local entity with this URL ID, the reference field will point to it (eg. node/456), if not, it will point to the remote source (eg. 'http://example2.com/node/123').
Furthermore, URL ID fields have fetchers – plugins that allow fetching remote data and saving it locally. These fetchers can also affect the reference link, for example by automatically download the referenced entity, or to redirect to the remote source.

This is a work in progress. It is related to a project for being able to download and sync help pages from drupal.org to your local site. See the following links for more information:

* Specification/wish list for better help system: http://drupal.org/node/1095012
* Better help system for Drupal 8: http://drupal.org/node/1031972
* Want the ability to create multiple outlines/maps: http://drupal.org/node/995370

Workflow entity and State field

D7 work on workflow module

I think this way we should go with workflow in D7:
1) Workflow is entity
2) State is field
3) Core actions, triggers integration
3) State formatter is configurable for displaying within entity view states
4) Access to none-workflow entity to view/change could be optional
5) Rules, views integration

Example Sandbox Module

This is Demo Project for our screen cast.


Blogsies is a complete blogging platform that handles all content types, views, and basic styling of a blog section. Using Context, Blogsies automatically creates a blog section and page, complete with a blog roll, category, tag, and recent post blocks. Each blog post supports tags, categories, related posts, header/teaser image, inline images, and a host of other features.

Expire Nodes

Expire Nodes is a set of modules which allow you to set expiration periods per node-based content type.

You can choose whether to unpublish and/or delete nodes of a given content type, a given number of days after creation. Nodes marked Sticky are not unpublished or deleted. Nodes will be unpublished or deleted on cron runs, or any system event that triggers hook_cron().

This module is for Drupal 7. It has no dependencies other than the node module. It does exactly what it says on the tin.

Expire Nodes UI is another module in this package. It lets you configure the expiration periods per content type. It exists as another module so that you can disable it for production sites.

This project is similar to a few other projects. Neither Auto Expire, nor Node Expire are in active development, and both seem to have stopped at Drupal 6.

Scheduler is still under active development, with a D7 version.

How to use Expire Nodes module:

0) Keep in mind: THIS MODULE WILL DELETE CONTENT, so be careful testing it.

1) Enable the modules.

2) Go to the Content Types admin page: /admin/structure/types

3) Choose a content type to auto-expire and click 'edit.'