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.
The XML sitemap module creates a sitemap that conforms to the sitemaps.org specification. This helps search engines to more intelligently crawl a website and keep their results up to date. The sitemap created by the module can be automatically submitted to Ask, Google, Bing (formerly Windows Live Search), and Yahoo! search engines. The module also comes with several submodules that can add sitemap links for content, menu items, taxonomy terms, and user profiles.
Views Slideshow can be used to create a slideshow of any content (not just images) that can appear in a View. Powered by jQuery, it is heavily customizable: you may choose slideshow settings for each View you create.
- News item slideshow (such as the title, image and teaser of the last 5 news articles submitted)
- The Last X number of X submitted (images, videos, blog entries, forum posts, comments, testimonials, etc.).
- Rotate any image, based on any filters you can apply in views.
- Hottest new products for any ecommerce drupal site.
- Rotate contact links, share links, etc.
- Heck, you could rotate entire nodes, categories, image galleries, etc. I wouldn't suggest it, but you have that power.
- Its also a great space saver. Places where you had multiple images or multiple items such as RSS feeds or category listings can now be presented in a slideshow.
The possibilities are really endless, as the more ways you can think of to categorize and add to views, the more you can rotate.
Views Slideshow Installation and Configuration
Colorbox is a light-weight customizable lightbox plugin for jQuery. This module allows for integration of Colorbox into Drupal.
Images, iframed or inline content etc. can be displayed in a overlay above the current page.
The Colorbox module:
- Works as a Formatter in entities and in views.
- Excellent integration with core image field and image styles and the Insert module
- Choose between a default style and a number of other styles that are included.
- Style the Colorbox with a custom Colorbox style in your theme.
- Drush command, drush colorbox-plugin, to download and install the Colorbox plugin in sites/all/libraries.
The Colorbox plugin:
- Supports photos, grouping, slideshow, ajax, inline, and iframed content.
- Appearance is controlled through CSS so it can be restyled.
- Can be extended with callbacks & event-hooks without altering the source files.
- Completely unobtrusive, options are set in the JS and require no changes to existing HTML.
- Preloads upcoming images in a photo group.
- Well vetted and currently in use in over 600,000 websites.
The advanced help module allows module developers to store their help outside the module system, in pure .html files. The files can be easily translated simply by copying them into the right translations directory. The entire system can appear in a popup or not as the module prefers (and by taking away access to view the popups, a site can force the popups to not exist).
The system ties into Drupal's search system and is fully indexed, so the entire contents can be searched for keywords. the help files can be placed in a hierarchy as well, allowing for top down navigation of the help.
By itself, this module doesn't do much; it requires another module to support it, but it does come with a nice little sample of text from Wikipedia to demonstrate the system.
When this module is installed, users with the
view advanced help index permission can access the advanced help index by going to Administer -> Advanced Help (
view advanced help popup and
view advanced help topic permissions enable them to access the actual help pages and popups.
The features module enables the capture and management of features in Drupal. A feature is a collection of Drupal entities which taken together satisfy a certain use-case.
Features provides a UI and API for taking different site building components from modules with exportables and bundling them together in a single feature module. A feature module is like any other Drupal module except that it declares its components (e.g. views, contexts, CCK fields, etc.) in its
.info file so that it can be checked, updated, or reverted programmatically.
Examples of features might be:
Currently supported editors
Patches to add support for other editors are welcome.
GlobalRedirect is a simple module which…
- Checks the current URL for an alias and does a 301 redirect to it if it is not being used.
- Checks the current URL for a trailing slash, removes it if present and repeats check 1 with the new request.
- Checks if the current URL is the same as the
site_frontpageand redirects to the frontpage if there is a match.
- Checks if the Clean URLs feature is enabled and then checks the current URL is being accessed using the clean method rather than the 'unclean' method.
- Checks access to the URL. If the user does not have access to the path, then no redirects are done. This helps avoid exposing private aliased node's.
- Make sure the case of the URL being accessed is the same as the one set by the author/administrator. For example, if you set the alias "articles/cake-making" to node/123, then the user can access the alias with any combination of case.
- Most of the above options are configurable in the settings page. In Drupal 5 you can access this after enabling the
globalredirect_adminmodule. In Drupal 6, the settings page is bundled into the module.
The Lightbox2 module is a simple, unobtrusive script used to overlay images on the current page. It's a snap to setup and works on most modern browsers.
The word "title" is a bit overloaded. Every piece of content in Drupal has a title, and so does every page. The page title is the one found in the HTML head inside the <title> tag. It is also used on SERPs (Search Engine Result Pages) and can greatly enhance your websites SEO (Search Engine Optimization).
This module gives you granular control over the page title. You can specify patterns for how the title should be structured and, on content creation pages, specify the page title separately to the content's title.
So… have you ever used the Main and Secondary menu links feature on your theme and wondered “how the hell do I display any menu items deeper than that?”
Well, that’s what this module does. It provides configurable blocks of menu trees starting with any level of any menu. And more!
This module augments Views by allowing bulk operations to be executed on the displayed rows. It does so by showing a checkbox in front of each node, and adding a select box containing operations that can be applied. Drupal Core or Rules actions can be used.
7.x-3.x requires Entity API.
TABLE OF CONTENTS
- Views 7.x-3.x works with VBO 7.x-3.x
- Views 6.x-2.x works with VBO 6.x-1.x
- Views 6.x-3.x works with VBO 6.x-1.10 and above
- VBO 6.x-3.x is obsolete
CREDITS AND SPONSORSHIP
Provides one-way string transliteration (romanization) and cleans file names during upload by replacing unwanted characters.
Generally spoken, it takes Unicode text and tries to represent it in US-ASCII characters (universally displayable, unaccented characters) by attempting to transliterate the pronunciation expressed by the text in some other writing system to Roman letters.
A wrapper module around the jQuery UI effects library that lets module developers add swooshy, swishy effects to their code.
See http://jqueryui.com/demos for some examples of what jQuery UI can do.
See http://jqueryui.com/docs for documentation on how to use it.
See http://jqueryui.com/support if you need help getting jQuery UI to work, once it's being added to your pages.
This is a utility module that won't do anything on its own. See README.txt for how your module can use it to add jQuery UI effects to your pages.
Since Drupal 7 ships with jQuery UI, the jQuery UI module has been deprecated and moved to the jQuery Update module.
The Media module provides an extensible framework for managing files and multimedia assets, regardless of whether they are hosted on your own site or a 3rd party site - it is commonly referred to as a 'file browser to the internet'.
Media is a drop-in replacement for the Drupal core upload field with a unified User Interface where editors and administrators can upload, manage, and reuse files and multimedia assets. Any files uploaded before Media was enabled will automatically take advantage of the many of the features it comes with.
Media's aim is to solve Drupal's long standing media handling problem.
What is the difference between 1.x and 2.x?
The 7.x-1.x version is the stable and recommended version for most users and production sites. It has reached feature freeze and will not be getting any new features, only bug fixes.
The 7.x-2.x version offers a lot of new improvements and is currently the active development version for new features and UI improvements. Bugs fixed in 7.x-2.x will also be fixed in 7.x-1.x if possible. See the wiki page on differences between the 1.x and 2.x versions for more detailed information.
This is a collection of modules to extend Drupal core multilingual capabilities and be able to build real life multilingual sites. Some features:
- Taxonomy translation (both, per language terms and translatable terms)
- Multilingual variables
- Multilingual blocks (control visibility per language and translate title and content)
- Language selection (when you switch the site language you'll see only the content for that language)
- Requires Variable module 2.x (Drupal 7)
Read a complete feature overview in the Internationalization handbook: Building multilingual sites .
Drupal 7 upgrade
Context 3.x for Drupal 6.x
Context allows you to manage contextual conditions and reactions for different portions of your site. You can think of each context as representing a "section" of your site. For each context, you can choose the conditions that trigger this context to be active and choose different aspects of Drupal that should react to this active context.
Think of conditions as a set of rules that are checked during page load to see what context is active. Any reactions that are associated with active contexts are then fired.
Other included modules
- Context UI provides an administrative interface for managing and editing Contexts. It is not necessary for the proper functioning of contexts once they are built and can be turned off on most production sites.
- Context layouts provides a formalized way for themes to declare and switch between page templates using Context. It is a continuation of an old Drupal themer's trick to switch to something besides the standard
page.tpl.phpfile for a variety of special case pages like the site frontpage, login page, admin section, etc.
This module will display any Views date field in calendar formats, including CCK date fields, node created or updated dates, etc. Switch between year, month, and day views. Back and next navigation is provided for all views. Lots of the Calendar functionality comes from the Date module, so any time you update the Calendar module you should be sure you also update to the latest version of the Date module at the same time.
See also Date iCal, a project that contains code and features needed to either import or export dates using iCal feeds. The functionality that used to be in the Calendar iCal module has been moved into that module.
Be sure to read Debugging Information before reporting a problem. Going through those steps may resolve your problems and will help provide enough information to tell if this is a bug.
The Metatag module allows you to automatically provide structured metadata, aka "meta tags", about your website. In the context of search engine optimization, when people refer to meta tags they are usually referring to the meta description tag and the meta keywords tag that may help improve the rankings and display of your site in search engine results.
This module provides a field type for email addresses.
- validation of emails
- turns addresses into mailto links
- encryption of email addresses with
- contact form (see Display settings)
- provides Tokens (for D 7.x: use Entity tokens from the Entity API)
- exposes fields to Views
- can be used with Rules
- Panels Integration
The basic email field type is in core now: #1668332: Add an E-mail field type into core, making this contrib module obsolete. Specific formatters (like the contact form) can live in separate contrib modules.
D6 to D7 Upgrade
- Run Core upgrade path
- Install Content Migrate from CCK
- Go to "Structure" -> "Migrate Fields"
- Select Email fields you want to upgrade and submit the "Migrate selected fields" button
Fieldgroup will, as the name implies, group fields together. All fieldable entities will have the possibility to add groups to wrap their fields together. Fieldgroup comes with default HTML wrappers like vertical tabs, horizontal tabs, accordions, fieldsets or div wrappers.
The field group project is a follow-up on the field group module in CCK. The release will only exist for Drupal 7 release and higher, so since the existence of the Fields API in core.
By moving field group to a separate module, this may open some new perspectives.
The 7.x-2.x branch will not be supported any longer:
- Moving horizontal tabs to the elements module was the plan but it seems this will be too late to accomplish
- CTools content type and Panels integration will be merged into 7.x-1.x
- HTML5 group type will be merged into 7.x-1.x
- Available preprocessor for fields will be merged into 7.x-1.x
Note: Current changes are made in the 1 branch.
Three styles/types of menus are currently possible: horizontal, menus drop down; vertical, menus fly to the left; vertical, menus fly to the right. There is a handbook page that provides a list of sites that use Nice menus.
Nice Menus creates blocks that may be associated with any existing site menu which can be placed wherever normal blocks can be placed in a theme. For themers, it is also possible to theme a menu as a Nice Menu directly by using the provided theme functions so a block is not necessary. A specific theme function for the Primary Links menu is available. The theme functions also allow a developer to pass in a custom menu tree of their making (i.e. not using a Drupal menu.) There is more information on how to use theme functions in the documentation.
This project allows you to add meta tags to Drupal pages, both manually and automatically based on various settings. Paying attention to meta tags, such as keywords, description and canonical URL, may help obtain better search engine positioning. The module aims to support the most useful meta tags, others may be created using the module's custom hooks.
Note: My current focus is on getting the D7 Metatag module to a stable point, at which point work will continue again on Nodewords.
The 6.x-2.x branch is currently unsupported
While forthcoming 6.x-1.14 release will probably be the final 6.x-1.x release, I've decided that the current 6.x-2.x branch (i.e. 6.x-2.0-alpha1) is no longer supported while I work out the module's future.
Variable module provides a registry for meta-data about Drupal variables and some extended Variable API and administration interface.
This is an API module so it must be installed only when other modules require it.
Module Developers: Please declare your variables.
This is a nice introduction to the module by Lullabot, Module Monday: Variable.
- So other modules can know about your module's variables and they can be translated, exported, used in views, etc.
- You'll get automatic variable edit forms, tokens, access control and uninstall for free
- Your module's variables will be allowed for Variable Realms being able to get values for each language (Internationalization) or Domain (Variable Domain)
Integrating with git checkouts
This module is based on concepts very similar to Drupal core's update module. Modules and themes with their corresponding drupal.org projects are identified and translations are downloaded for the appropriate versions. If you use git checkouts instead of package tarballs or zip files, use Git deploy module, so projects and versions are identified properly. (For legacy CVS checkouts, the CVS deploy module will work).
- Big translation files might run into your PHP timeout (#569004).