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.
This suite is primarily a set of APIs and tools to improve the developer experience. It also contains a module called the Page Manager whose job is to manage pages. In particular it manages panel pages, but as it grows it will be able to manage far more than just Panels.
For the moment, it includes the following tools:
- Plugins -- tools to make it easy for modules to let other modules implement plugins from .inc files.
- Exportables -- tools to make it easier for modules to have objects that live in database or live in code, such as 'default views'.
- AJAX responder -- tools to make it easier for the server to handle AJAX requests and tell the client what to do with them.
- Form tools -- tools to make it easier for forms to deal with AJAX.
- Object caching -- tool to make it easier to edit an object across multiple page requests and cache the editing work.
- Contexts -- the notion of wrapping objects in a unified wrapper and providing an API to create and accept these contexts as input.
- Modal dialog -- tool to make it simple to put a form in a modal dialog.
- Dependent -- a simple form widget to make form items appear and disappear based upon the selections in another item.
- Content -- pluggable content types used as panes in Panels and other modules like Dashboard.
The Pathauto module automatically generates URL/path aliases for various kinds of content (nodes, taxonomy terms, users) without requiring the user to manually specify the path alias. This allows you to have URL aliases like /category/my-node-title instead of /node/123. The aliases are based upon a "pattern" system that uses tokens which the administrator can change.
Provides a theme-independent administration interface (aka.
back-end). It's a helper for novice users coming from other CMS, a time-saver for site administrators, and useful for developers and site builders.
Administrative links are displayed in a CSS/JS-based menu at the top on all pages of your site. It not only contains regular menu items — tasks and actions are also included, enabling fast access to any administrative resource your Drupal site provides.
Allows to use client-side editors to edit content. It simplifies the installation and integration of the editor of your choice. This module replaces all other editor integration modules. No other Drupal module is required.
Wysiwyg module is capable to support any kind of client-side editor. It can be a HTML-editor (a.k.a. WYSIWYG), a
pseudo-editor (buttons to insert markup into a textarea), or even Flash-based applications. The editor library needs to be downloaded separately. Various editors are supported (see below).
Wysiwyg module also provides an abstraction layer for other Drupal modules to integrate with any editor. This means that other Drupal modules can expose content-editing functionality, regardless of which editor you have installed.
This module will allow Drupal to replace textarea fields with the CKEditor - a visual HTML editor, sometimes called WYSIWYG editor. This HTML text editor brings many of the powerful WYSIWYG editing functions of known desktop editors like Word to the web. It's very fast and doesn't require any kind of installation on the client computer.
What is CKEditor?
CKEditor is the next version of FCKeditor. The editor has been rebranded and completely rewritten. It is now much faster (the code has been optimized), loads faster (the number of files has been reduced, so the browser will perform less HTTP requests) and developers friendly. See the list of features.
A suite of modules containing fun for module developers and themers ...
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:
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.
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.
What is Content Access?
Yet another content access module.
This module allows you to manage permissions for content types by role and author. It allows you to specifiy custom view, edit and delete permissions for each content type. Optionally you can enable per content access settings, so you can customize the access for each content node.
- It comes with sensible defaults, so you need not configure anything and everything stays working
- It is as flexible as you want. It can work with per content type settings, per content node settings as well as with flexible Access Control Lists.
- It tries to reuse existing functionality instead of reimplementing it. So one can install the ACL module and set per user access control settings per content node.
Furthermore the module provides conditions and actions for workflow-ng / rules, which allows one to configure even rule-based access permissions.
- It optimizes the written content node grants, so that only the really necessary grants are written. This is important for the performance of your site.
- It takes access control as important as it is. E.g. the module has a bunch of simpletests to ensure everything is working right.
The modules list page can become quite big when dealing with a fairly large site or even just a dev site meant for testing new and various modules being considered. What this module aims to accomplish is the ability to quickly find the module you are looking for without having to rely on the browsers search feature which more times than not shows you the module name in the 'Required by' or 'Depends on' sections of the various modules or even some other location on the page like a menu item.
When tabs is enabled via the Module Filter's settings page, a new module layout theme is implemented. This tab layout provides a tab for each package as well as a tab that will show every module alphabetically. The filter textfield is available on each tab but currently doesn't support autocomplete.
This module adds a tab for sufficiently permissioned users. The tab shows all revisions like standard Drupal but it also allows pretty viewing of all added/changed/deleted words between revisions.
- Moshe Weitzman (moshe)
Refer to the readme.txt for configuration options.
This module allows you to specify a redirect from one path to another path or an external URL, using any HTTP redirect status.
This simple module allows you to specify some additional attributes for menu items such as id, name, class, style, and rel.
You should use this module when
- You want to "nofollow" certain menu items to sculpt the flow of PageRank through your site
- You want to give a menu item an ID so you can easily select it using jQuery
- You want to add additional classes or styles to a menu item
The module currently allows you to set the following attributes for each menu item:
This module provides a powerful interface for managing taxonomies. A vocabulary gets displayed in a dynamic tree view, where parent terms can be expanded to list their nested child terms or can be collapsed.
The Taxonomy Manager has following operations and key features:
- dynamic treeview
- mass deleting
- mass adding of new terms
- moving of terms in hierarchies
- merging of terms (using the Term merge module in 7.x)
- fast weight changing with up and down arrows (and AJAX saving)
- AJAX powered term editing form
- simple search interface
- CSV Export of terms
- i18n support for multilingual vocabularies (per language terms)
- Double Tree interface for moving terms in hierarchies, adding new translations and switching terms between different vocabularies
Taxonomy Manager Drupal 5 and JQuery Upadate module:
This module assists with the site/domain ownership authentication/verification for search engines. There are two types of verification methods supported: adding meta tags, or uploading a specific file. If you are provided with a file to upload, this module makes it easy because you can upload the file in the module's interface and the proper filename and file contents will be saved and used in the authentication process.
This module is useful for the following search engine verifications:
Drupal SEO Checklist - What is it?
The Drupal SEO Checklist uses Drupal SEO best practices to check your website for proper search engine optimization. It eliminates guesswork by creating a functional to-do list of modules and tasks that remain. Updated regularly with the latest techniques, it makes on-page Drupal search engine optimization hassle-free.
It breaks the tasks down into functional needs like Title Tags, Paths, Content and many more. Next to each task is a link to download the module from D.o and a link to the proper admin screen of your website so that you can configure the settings perfectly.
Drupal SEO Checklist also keeps track of what has already been done. It places a date and time stamp next to each item (when you click save). That provides a simple report that you can share with others showing what's been done.
You need Drupal SEO Checklist if
- You know SEO basics pretty well
- You work on a lot of different websites and need help keeping track of what you've done on each
- You know how to properly configure modules for SEO needs
- You are a list-maker! Or, you simply enjoy checking things off when they're done.
Drupal SEO Checklist does not:
- Provide good SEO strategy
#D7CX This module got into core and will only be available as a back-port version for Drupal 6.
Provides vertical tabs like http://drupal.geek.nz/static/node-form/default/summaries2.html on the node add form.
This module provides the following features:
- Vertical tabifying all node forms.
- Vertical tabifying the content type forms.
- Vertical tabifying the block forms.
- Specialized CSS for Garland, as well as generic CSS for other themes
- Color module support when both Garland and color.module are used
- Vertical tabbed forms and fieldsets are over-ridable by using your site's settings.php and $conf. For more information see #644790-7: Simplify the module and integrate with form_controller to allow customizations.
- When used in combination with Form module allows you to configure vertical tabs on all possible forms.
The masquerade module is designed as a tool for site designers and site administrators. It allows a user with the right permissions to switch users. While masquerading, a field is set on the $user object, and a menu item appears allowing the user to switch back. Watchdog entries are made any time a user masquerades or stops masquerading.
Provides a quick and easy way to replace any text on the site.
- Easily replace anything that's passed through t()
- Locale support, allowing you to override strings in any language
- Ability to import/export *.po files, for easy migration from the Locale module
- Note that this is not a replacement to Locale as having thousands of overrides can cause more pain then benefit. Use this only if you need a few easy text changes.
OAuth implements the OAuth standard for use with Drupal and acts as a support module for other modules that wish to use OAuth.
Version 3.x is an entirely new module, previously known as OAuth Common, that takes an extended approach to dealing with OAuth. Not compatible with older versions of the OAuth module.
What is Delta?
Delta allows you, via the Context module to make duplicates of your theme settings for any context on your site. This gives you the ability for alternative layouts as a reaction in Context... </awesomesauce>
Delta by definition: (Greek letters in mathmatics)
- a finite difference
- a difference operator
- a symmetric difference
- the difference or change in a given variable
Currently no status messages of great importance other than the fact that there IS finally a release of Delta... ;)
This module defines the "hierarchical_select" form element, which is a greatly enhanced way for letting the user select items in a hierarchy.
Hierarchical Select has the ability to save the entire lineage of a selection or only the "deepest" selection. You can configure it to force the user to make a selection as deep as possible in the tree, or allow the user to select an item anywhere in the tree. Levels can be labeled, you can configure limit the number of items that can be selected, configure a title for the dropbox, choose a site-wide animation delay, and so on. You can even create new items and levels through Hierarchical Select!
For a good overview of what Hierarchical Select can do, look at this demo!
I'm focusing on maintaining only the Drupal 7 version of Hierarchical Select. That means I'll only commit RTBC patches for the D6 version relatively quickly. If a co-maintainer steps up to help maintain the Drupal 6, I'd be happy to accept him/her! :)
Drupal 7 version
The Drupal 7 version integrates with:
- Taxonomy (Drupal core)
- Menu (Drupal core)