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.
ImageCache allows you to setup presets for image processing. If an ImageCache derivative doesn't exist the web server's rewrite rules will pass the request to Drupal which in turn hands it off to ImageCache to dynamically generate the file.
This project provides D7 versions of the 'node_reference' and 'user_reference' field types, that were part of the CCK package in D6, at functional parity with the D6 counterparts. See http://drupal.org/node/533222 for details.
Note for users upgrading from References 7.x-2.0-beta3
There were a couple changes in the way 'References' views are handled ("referenceable nodes/users defined by a view"), which might require double-checking those existing on your site:
The 'label' (node title or user name) is no longer automatically added if not included in the view. If some of your 'References' views currently do not include it, you might want to add it explicitly, else it will no longer appear in the widgets.
The HTML generated by the view is no longer stripped out before being handed to "checkboxes / radios" widgets, thus allowing advanced formatting. You might want to check for Reference views having fields configured to display "as links", since the (probably unwanted) <a> tags generated by Views are not removed anymore.
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.
Block Class allows users to add classes to any block through the block's configuration interface. By adding a very short snippet of PHP to a theme's block.tpl.php file, classes can be added to the parent <div class="block ..."> element of a block. Hooray for more powerful block theming!
This module provides a suite of additional image effects that can be added to image styles. The image styles admin submodule also adds the 'duplicate', 'export' and 'import' actions to image styles administration.
"auto_nodetitle" is a small and efficient module that allows hiding of the content title field in the form. To prevent empty content title fields one can configure it to generate the title by a given pattern.
This module was previously known as FileField Insert.
This is a Mime Mail component module (for use by other modules).
It permits users to receive HTML email and can be used by other modules. The mail functionality accepts an HTML message body, mime-endcodes it and sends it.
If the HTML has embedded graphics, these graphics are MIME-encoded and included as a message attachment.
Adopts your site's style by automatically including your theme's stylesheet files in a themeable HTML message format
If the recipient's preference is available and they prefer plaintext, the HTML will be converted to plain text and sent as-is. Otherwise, the email will be sent in themeable HTML with a plaintext alternative.
Allows you to theme messages with a specific mailkey.
Converts CSS styles into inline style attributes.
Provides simple system actions and Rules actions to send HTML email with embedded images and attachments.
Note that there are some serious limitations you need to take into consideration when creating email layouts, see the Email Standard Project for more information.
The Quick Tabs module allows you to create blocks of tabbed content, specifically views, blocks, nodes* and other quicktabs*. You can create a block on your site containing multiple tabs with corresponding content. Clicking on the tabs makes the corresponding content display instantly, using jQuery. With the 6.x-2.x branch, this can be done in either ajax or non-ajax mode:
File entity provides interfaces for managing files. It also extends the core file entity, allowing files to be fieldable, grouped into types, viewed (using display modes) and formatted using field formatters. File entity integrates with a number of modules, exposing files to Views, Entity API, Token and more.
File Entity is required by the 7.x-2.x branch of the Media module.
The File entity project is not compatible with Media 7.x-1.x. You must use the File entity module bundled with Media 7.x-1.x.
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 clone module allows users to make a copy of an existing item of site content (a node) and then edit that copy. The authorship is set to the current user, the menu and url aliases are reset, and the words "Clone of" are inserted into the title to remind you that you are not editing the original content.