36,686 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.

Phone

This module provides a phone field type

You should probably consider using https://www.drupal.org/project/telephone instead. Eventually, the validation and formatting features of this module will be moved into a new module that extends the telephone module in both D7 and D8.

Checklist API

Example checklist

Checklist API Provides a simple interface for modules to create fillable, persistent checklists that track progress with completion times and users. You don't need this unless you're a module developer or you want to use a module that calls for it.

Nodeblock

This module allows you to specify content type(s) as being a block. This allows the content managers of the site to edit the block text and title without having to access the block administration page. Users only need edit access to that node in order to edit it.

We advice you to use this module together with Node Level Blocks or Block Reference module.

It is very handy to create a simple block content type and enable this content type for blocks and use these in place of the normal 'add block' functionality.

Now supports translatable content (Contrent translation with i18n and Entity Translation)

If Content Translation is enabled, then only a single node block per translation set is exposed and the node from the translation set with the appropriate language is loaded into the block.

Other modules

There are several other modules and approaches that allow nodes to be presented as a block. See a comparison at http://groups.drupal.org/node/93499

Drupal 7

The Drupal 7 version of this module enables the use of view modes. This gives the user even greater control over customizing the output of the node block. Default view modes and links display can now be assigned per content type and then overridden at block/node level.

Drupal 6

jQuery plugins

The jquery_plugin module provides miscellaneous jQuery plugins, which can be loaded from any module or theme by calling jquery_plugin_add($plugin) in Drupal 6 or drupal_add_library('jquery_plugin', $plugin) in Drupal 7. The Drupal 6 version supports jQ, a jQuery plugin registry.

Viewfield

Viewfield provides a field that holds a reference to a View and renders it whenever the entity containing the field is displayed.

Features

  • Author chooses a view and display from a list.
  • View arguments are supplied through tokens.
  • Administrators may restrict which views may be assigned.
  • Administrators may supply a common value that will be used for all entities in a content type.

Advanced CSS/JS Aggregation

List of modules included

7.x & 8.x

Summary (7.x & 8.x)
AdvAgg allows you to improve the frontend performance of your site. Be sure to do a before and after comparison by using Google's PageSpeed Insights and WebPagetest.org. The performance benefits are achieved by using some of the features found in AdvAgg and its sub modules. Out of the box AdvAgg's frontend performance will be similar to cores.

Webform Ajax

Overview

This module adds AJAX support to Webform (3.0 and above).

As a first step it focusses to simply add form AJAX paging and submit. Form submissions get ajaxified including prev/next pages. Especially for multipage forms, this leads to faster loading (less data transfer), better usability and finally smaller server load.

There's no backport to previous versions on our roadmap and features are D7 only.

Documentation

Enable the module. You'll be able to configure AJAX enable per form in the advanced form settings.

Known problems

Credits

Role Delegation

Example of permissions added by Role Delegation

This module allows site administrators to grant specific roles the authority to assign selected roles to users, without them needing the administer permissions permission.

Views Infinite Scroll

Views infinite scroll allows you to load and display pages of any view inline, using AJAX (this has been called infinite scrolling, load more, autopaging, endless pages and more). The pager can be triggered with the press of a button or automatically as the user scrolls to the bottom of the view's content.

The Drupal 8 version of Views Infinite Scroll is a lightweight solution which:

Shortcode

Shortcodes are actually macros to be used in the text of contents. These macros change the text of the content and format the given part through the theme engine. This module defines few basic shortcodes only. (New ones will come.)

Shortcode is an API that handles the shortcode macros for text formats. You can add your own shortcode tags via this API. All tags are themeable and new tags can be provided by other modules.

Initial work is based on the Wordpress Shortcode API but was reworked for Drupal. You can nest tags (within same tags too), no need for special recursion handling.

Macros come with this module

Shortcode basic tags module

  • [quote] Replace the given text formatted like as a quote.
  • [img] Show an image.
  • [highlight] Insert a span with highlight css class around the text.
  • [button] Insert a link formatted like as a button.
  • [dropcap] Replace the given text formatted like as a dropcap.
  • [item] Insert div or span around the text with some css classes.'
  • [clear] Insert a float-clearing div for a proper layout.
  • [link] Makes an aliased link to the given path.

Password Policy

This module provides a way to enforce restrictions on user passwords by defining password policies.

Overview

A password policy can be defined with a set of constraints which must be met before a user password change will be accepted. Each constraint has a parameter allowing for the minimum number of valid conditions which must be met before the constraint is satisfied.

Real Name

The RealName module allows the administrator to choose fields from the user profile that will be used to add a "real name" element (method) to a user object. Hook_user is used to automatically add this to any user object that is loaded. It will also optionally set all nodes and comments to show this name.

Link checker

Link checker configuration UI

The Link checker module extracts links from your content when saved and periodically tries to detect broken hypertext links by checking the remote sites and evaluating the HTTP response codes. It shows all broken links in the reports/logs section and on the content edit page, if a link check has been failed. An author specific broken links report is also available in "My Account".

Features:

  • Selectively scan node types and comments
  • Selectively scan custom blocks
  • Scans CCK text and link fields in selected nodes
  • Checks internal and by default external links
  • Parallel link checking with optional HTTPRL module
  • Configurable link check intervals
  • Can update permanently moved (301) links after specified link check fail count
  • Can unpublish nodes after specified file not found (404) fail count
  • Output created by input filters is supported
  • Supported HTML elements: a, area, audio, embed, iframe, img, object, param, source, video
  • Supported link protocols: http, https
  • D6: Weblink nodes from Links Package module are supported
  • D6: Weblinks nodes from Weblinks module are supported

Menu position

Screenshot of content placed with Menu position module

Often times site builders want certain types of content to appear in a specific position in the navigational menu. The simplest solution, adding all of that content individually to the menu system, has performance and usability issues. (Imagine hundreds of menu items added to one spot in the menu.)

This module allows for the creation of rules that will dynamically add the current page into the menu system at the requested spots.

This includes affecting:

  • The main links of the theme
  • The secondary links of the theme
  • The breadcrumb trail
  • Menu blocks provided by core's Menu module
  • Menu blocks provided by the Menu Block module

Cache Expiration

Common settings form, module settings

This module provides configurable actions upon events that will expire URLs from caches like reverse proxy caches, internal page caches, etc.This module make more sense when Minimum Cache Lifetime setting is set to a value other than none.

There is now integration with the following modules:

  • Boost - deletes expired pages (files) from the file system.
  • Varnish - integrates over an administrative socket.
  • Fastly - Varnish/CDN caching
  • Purge - expires urls by sending purge requests to Varnish, Squid and Nginx over HTTP.
  • Acquia Purge - allows Drupal sites hosted on Acquia Cloud to automatically purge pages from their Varnish powered load balancers..
  • Memcache Storage - allows to delete pages that were cached in a memcached instances.
  • Akamai - provides an integration with the Akamai Cache Control Utility (CCU) Web Service
  • Recacher - Page cache warmer.

Module's features may extend if next modules are enabled:

  • Drush - provides drush commands to expire urls (xp-url), paths (xp-path), nodes (xp-node), users (xp-user), comments (xp-comment) from the command line shell and scripts.
  • Rules - provides actions for the Rules module to allow more advanced cache expiration scenarios.
  • Token - provides modal dialog with list of available tokens.
  • References and Entity reference - module may expire referenced entities' urls.

Message

UAS (User activity stream) example

The Message module is the core of the message stack. It enables logging and displaying system events in a number of different use cases. Events that are recorded over time are sometimes call activity streams. Exportable messages subtypes can be created for different use cases with custom fields and display (view) modes.

Entity cache

Entity cache puts core entities into Drupal's cache API.

Due to the entity loading changes in Drupal 7, no core patches are required.

How to use it

This module has no user interface, if you enable it, entities will start being cached, if you disable it, they'll stop.

Supported core entities

  • Nodes
  • Comments
  • Taxonomy terms
  • Taxonomy vocabularies
  • Files
  • Users

Support for contrib entities:

There is no automated support for contrib entities, to use entitycache for a contrib or custom entity:

  • Create a cache_entity_$myentity table/bin.
  • Specify EntityCacheDefaultEntityController as your controller class in hook_entity_info(), or extend it.
  • Never update your entity tables outside of save/delete API calls.

Tests

Entity cache is now set up for automated testing on Drupal.org, see current HEAD status.

This module is being developed for Drupal 7, and will never be backported to Drupal 6. For Drupal 6 you may want to look at this pressflow merge request or http://drupal.org/project/advcache.

Taxonomy display

Taxonomy display configuration form

The taxonomy display module allows administrative configurable term display pages. This allows administrators to override the default presentation of taxonomy term pages per vocabulary through the taxonomy term page's manage display form.

Hook into taxonomy term pages

Taxonomy display exposes three plugin types for modules to overwrite portions of taxonomy term pages by providing their own plugins. These plugins are selectable on a per vocabulary basis, allowing the site administrator to decide which plugins they want to display for each vocabulary. To learn how to provide your own plugins see the developer resources page.

Selectable term displays

  • Core

    • Plays nicely with Display suite.
    • Does not conflict with modules that make use of hook_taxonomy_term_view_alter(), hook_entity_view(), or hook_entity_view_alter().
  • Hidden

Selectable associated content displays

  • Core

    Embedded Media Field

    Maintainers: aaron (Aaron Winborn) and Alex UA (Alex Urevick-Ackelsberg)

    This extensible module will create fields for content types that can be used to display video, image, and audio files from various third party providers. When entering the content, the user will simply paste the URL or embed code from the third party, and the module will automatically determine which content provider is being used. When displaying the content, the proper embedding format will be used.

    The module is only an engine, and requires a supported module to function. These include 'Embedded Image Field', 'Embedded Video Field' and 'Embedded Audio Field'. These modules are included in the contrib folder of the module, so they can be easily activated from the module administration page.

    Please note: As of emfield 2.x, provider files for these modules are no longer included with the main emfield module, and must be downloaded separately- please see the list of projects providing provider files below.

    Modules extending Embedded Media Field

    The following modules work in conjunction with this project, largely to expose media providers (you'll need at least one of these to make the module useful):

    Media: 8Tracks
    Media: Archive

    Imagecache Token

    This module provides additional tokens for image fields. For each image style available, a token [node:field_image_field:style_name] will be provided. It is also possible to get image properties like width or height by using tokens like [node:field_image_field:style_name:height].

    Configuration

    No module configuration needed.

    Gotchas

    I've observed that after you create new image style it might not appear immediately in available tokens list. If this is a case, you will need to reset cache at Performance page.

    Email Registration

    Allow users to register and login using only an email address. Users can then log-in using their email address and password for authentication.

    Views Load More

    Yes, this is indeed, Yet another load more pager for views.

    This module has some very key differences then the other load more module.

    • Provide ajax/no-ajax views load more
    • Works with views default ajax implementation, no hacks (check/uncheck ajax)
    • Supports the Waypoints module for loading on various points, Such as when the scroller is visable on the page.
    • Supports the Fade effect when loading new content.

    Install the Waypoints module for extra features.

    Manual Crop

    Manual Crop

    The Manual Crop module exposes a set of image style effects that enables users, if enabled in the widget settings, to crop (and scale) an image after uploading.

    Colorbox Node

    Gives the user the ability to display ANY page inside a colorbox modal without the header and footer.

    Menu item visibility

    1309375059796.png

    This module exposes configurable and extendable visibility settings for menu links. For example, if you want to create a 'My account' link that points to /user, both anonymous and registered users have access to the /user path, so both will see the link, even if anonymous users do not technically have an account. Using this module will allow you to only have your 'My account' link visible to registered users, and hide it from anonymous users.

    The module uses the exact same UI used for block visibility settings for familiarity.

    Pages