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 Webform2PDF Drupal module is an extension of the Webform module. It can be used to generate PDF document from the results of a form. The generated PDF document can be attached to the form summary e-mail sent by Webform module, or it can be downloaded from the /Results/ page. Different PDF templates can be set for each form. The templates can be formatted with HTML tags, and they can be edited with WYSIWYG Drupal module, making the template creation easy and the templates highly customizable.
FeedAPI aggregates feeds on a Drupal website by generating light weight items or nodes from feeds. It provides a straightforward configuration for most use cases and is extensible through an API. FeedAPI integrates with OG (but does not require it).
This is a simple module for Drupal 7.x that uses jQuery to transform the TITLE or ALT attribute of a image to a image caption. There is a settings page with lot's of possible configuration. The image caption won't show in the WYSIWYG-editor, but will be visible when you view the node.
The module differs in several ways from similar modules.
The Internal Links module, Intlinks, is a simple set (currently two) of input filters which modify the output of internal, root-relative links in any text input format for which they are enabled. The title filter allows you to have the node titles of linked content automatically inserted into the link as the HTML "title" attribute, with "node/123" -type href paths converted to URL aliases, too. It is especially useful for streamlining the editorial workflow and improving SEO. You can also use the "Hide bad" filter to "unlink" unpublished content so visitors don’t encounter "page not found" errors.
The Publication Date module adds a "Published on" date for each node, containing the date when it was first published.
Without this, the only dates available for nodes are their created date and changed date, but these are often insufficient to meet the needs of publishing workflows. Sorting nodes by their created date doesn't account for content which is held in draft form for a time while being readied for publication. Sorting nodes by their changed date fails to account for content needing minor corrections after being published.
This module provides a WYSIWYG editor using the CKEditor library. While there are other approaches to integrating CKEditor into Drupal (through either the WYSIWYG module or CKEditor module), this project takes a combination approach mixing the best from WYSIWYG module (generic bindings to text formats) with tight direct integration with Drupal. The current version of CKEditor bundled is 4.2.
This module is currently experimental. It does not yet integrate with any existing 3rd party modules such as Media or WYSIWYG Fields. Support for these modules is planned through WYSIWYG API for Drupal 7, but not yet integrated.
Bundled lightweight CKEditor 4.x version, optimized for Drupal integration (no unneeded plugins makes for faster loading). No need to download the editor separately.
Additional add-on plugins that tightly integrate Drupal with CKEditor
Drupal Image plugin
Drupal Image captioning plugin
Webkit Resize plugin (adds support for resize handles in Chrome/Safari)
Dependency on WYSIWYG module keeps compatibility with other WYSIWYG editors
Uses absolutely no inline styles. All buttons and cleanup uses a consistent set of classes which can be themed.
Mailhandler uses Feeds to let you post nodes by email. It takes mail (usually from an IMAP mailbox) and imports it as whatever type of content you choose. Plug-in modules allow you to do more awesome things like post comments, select different authentication methods, and set properties such as published / sticky status using "commands". Hugely powerful and flexible, but includes a "quick-start" module to help get you started.
Inline module allows users to display uploaded files and images inline, i.e. place links to files into a content using a simple [inline:filename.jpg] tag. The effect is a link to the file or the display of an image, depending on the file type.
Inline allows users to place an uploaded image or a file attachment anywhere in the content. During creation of a content, a user can simply enter the number or filename of the attachment that should be displayed inline. After submitting the content, the number is automatically converted to the corresponding filename.
#D7CX: I pledge that Wikitools will have a full Drupal 7 release on the day that Drupal 7 is released.
The wikitools module provides some settings to get a more wiki-like behavior. It aims to be lightweight; all features are optional, and it provides no database tables of its own. If you have ideas about cool new features for this module, please post an issue. All new features go into the 6.x branch; I encourage others to present patches with backports. Some of the features of this module are:
Feeds Image Grabber (FIG) is successor of FeedAPI ImageGrabber, an addon for Feeds module, which grabs image for each feed-item from their respective webpages and maps it to an image field in the node created by Feeds (Node Processor).
[Google Reader (with thumbnails) can be imitated on a Drupal site by using Feeds, Feeds Image Grabber, FileField, ImageField, ImageCache, ImageAPI, Views and Voting API module (http://goo.gl/J5MJg)]
Automatically downloads and attaches image to the node created by Feeds module.
Configurable XPath of the desired image location on the webpage of the feed item on per feed basis (using element's id or CSS class).
Copy webform configuration from one node to another
This is an add-on module for Webform that allows you to select webform enabled content types as "source" and/or "destination" types. On node edit/creation of the so called "destination" types, you have to option to apply (= copy) the webform settings (including all webform fields) from nodes of the "source" type.
That way you can easily copy webform configuration from one node to another.
However, if you want regular fields attached to the node to copy (e.g., the body field), you should use the Node clone module.
Webform is the module for making surveys in Drupal. After a submission, users may be sent an e-mail "receipt" as well as sending a notification to administrators. Results can be exported into Excel or other spreadsheet applications. Webform also provides some basic statistical review and has and extensive API for expanding its features.
The Featured Content module lets you very easily create related/featured content blocks on your Drupal site. This module is useful if you have non-technical users who need to add blocks on the site that contain lists of node titles, node teasers, and/or full node content. This module can also be useful if you need to get up some featured/related content blocks quickly and are not familiar enough with views to do it, or simply prefer not to use views for this purpose. A related/featured content block can be created in just a few minutes.
Language support was added in version 1.5 for both D6 & D7. If you have a multilingual website, please use 1.5 or above.
Do not use the 6.x-2.x-dev and 7.x-2.x-dev branches as they are for experimenting with performance enhancements. If you want to grab a *dev* version (which we try to keep stable), then grab the 1.x version in the downloads section.
NOTE: If you have a large site (lots of nodes and/or users), this module will likely NOT be a good fit as there is currently NO caching (views is recommended in that case). If someone is interested in becoming a co-maintainer and working on the caching code (in the 2.x branch), please add an issue to the queue. Thanks!
This project seeks to provide a true compound field solution for Drupal 7. As much as I love Field collection, it still has to save actual entities, and can cause performance problems due to having to load all the referenced field collection entities on node, or parent entity load.