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 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.
Advanced Forum builds on and enhances Drupal's core forum module. When used in combination with other Drupal contributed modules, many of which are automatically used by Advanced Forum, you can achieve much of what stand alone software provides. Because it uses the core forum module, it uses the node and comment system built into Drupal and is completely integrated, not a bridge. While it doesn't have all of the features of stand alone forum applications, being completely integrated into your site provides advantages that they don't.
Skinr's main purpose is to allow the theme to define a set of reusable and modular CSS styles, and to make those styles available in Drupal's UI. Skinr was developed for themers to allow them to tap into the power of Drupal's modularity and apply those same principals to theme development. It does not provide any styles of its own. These styles are defined in the .info file of the theme (or subtheme), by the themer and end up in various places in Drupal's UI, such as:
It also provides a CSS class field, where you can manually add custom classes.
Tagadelic provides an API and a few simple turnkey modules, which allows you to easily create tagclouds, weighted lists, search-clouds and such.
With the API you can build a module with a few lines of PHP, to turn anything that can be counted into a weighted cloud. Which can be presented to your users anyway and anywhere on your site.
With the turnkey modules, you can add a page that shows taxonomy-terms in a weighted cloud: terms that are used more often are bigger. Another module provides a page that shows article-titles in a cloud: titles from articles that are read more often appear bigger.
Tagadelic 2.x branch is work in progress and should only be used by people who plan to develop for and with it.
Tagadelic 1.x branch is stable for Drupal 6 but unstable for Drupal 7. End-users should use Drupal 6, 6.x-1.x versions. End-users are strongly advised not to use Drupal 7, 7.x-1.x of tagadelic; it has known bugs, yet is reported to work for some people. Use at own risk.
The Login Destination module allows you to customize the destination that a user is redirected to after logging in, registering to the site (7.x), using a one-time login link or logging out (7.x). The destination can be an internal page or an external URL. It is possible to specify certain conditions like referring pages or user roles and make the destination depend upon them. You may use PHP snippets to provide custom conditions and destinations. It is also possible to keep users on the currently visited page after logging in or out.
DISCLAIMER: Do not use Omega Tools with the 4.x version of Omega. While it might work it is not tested and possibly incompatible. Please create your 4.x subthemes using Drush! The Drush integration for Omega 4.x comes as part of the theme itself and does NOT require Omega Tools. Please uninstall Omega Tools if you are building a site with Omega 4.x
The Omega Tools module is a set of helper functions and custom functionality intended for use with the Omega Theme. However, the functions this module provides could be used with any theme.
This module is currently only being updated for the Drupal 7 branch, and for integrations with Drupal 7 Omega theme. Just sayin'.
The following features are provided by the Omega Tools module. Some features are Drupal 7 only, some are for Drupal 6 and 7 versions.
Flag is a flexible flagging system that is completely customizable by the administrator. Using this module, the site administrator can provide any number of flags for nodes, comments, users, and any other type of entity. Some possibilities include bookmarks, marking important, friends, or flag as offensive. With extensive views integration, you can create custom lists of popular content or keep tabs on important content.
Flags may be per-user, meaning that each user can mark an item individually, or global, meaning that the item is either marked or it is not marked, and any user who changes that changes it for everyone.
In this way, additional flags (similar to published and sticky) can be put on nodes, or other items, and dealt with by the system however the administration likes.
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
Computed Field is a very powerful CCK field module that lets you add a custom "computed fields" to your content types. These computed fields are populated with values that you define via PHP code. You may draw on anything available to Drupal, including other fields, the current user, database tables, you name it. (Feeling the power yet? :) ) You can also choose whether to store your computed field values in the database with other content fields, or have them "calculated" on the fly during node views. (Although you should note that Views use requires database stored values.) This field is literally the Swiss Army knife of CCK fields. So start cooking up your PHP based values!
Instead of showing a standard "404 Page not found", this module performs a search on the keywords in the URL, e.g. if a user goes to http://example.com/does/not/exist, this module will do a search for "does not exist" and shows the result of the search instead of the 404 page. This should help retain visitors coming in from old URLs linked from other sites or from search indices.
It also includes search engine keywords detections as well as regular expression based term filtering from the URL.
The Fivestar voting module adds a clean, attractive voting widget to nodes in Drupal 5, node and comments in Drupal 6, and any entity in Drupal 7. Developed by Lullabot and an officially supported module in Acquia Drupal.
- jQuery rollover effects and AJAX no-reload voting
- Configurable star sets
- Support for anonymous voters
- Spam protection to keep users from filling your DB with bogus votes
- Easy-to-use integration with Views module for lists sorted by rating, or filtered by min/max ratings
- A Fivestar CCK field for use in custom node types
- An easy-to-use Form API element type for use in other modules
- Compatible with all versions of jQuery (1.0 - 1.4.4)
IMCE Mkdir allows users to create and delete sub-directories under directories assigned by IMCE.
CONFIGURING AND USING
1. Go to admin/settings/imce Assuming you have already created a IMCE profile. Under section 'Configuration profiles' click on approprate 'Edit' link.
2. On the next page find section 'Directories'. Set appropriate permission using the check boxes 'Add subdirectories' and 'Remove subdirectories'.
3. Click on 'Save configuration' button.
4. To test use IMCE. A new 'Manage directories' tab button will be display. Follow instructions on screen.
@font-your-face provides an administrative interface for browsing and applying web fonts (using CSS @font-face, supported in all popular browsers) from a variety of sources. Try it out on simplytest.me.
- A font browsing interface allows selection of fonts from from several providers:
- Fonts are automatically loaded on site simply by clicking "Enable"; no need to create font files, write CSS, add JS, nor figure out different methods for every font provider.
- Clear indication of license restrictions on provided fonts.
- Fonts can be applied to specific text on the site either by using the provided font-family identifier in theme CSS, or by typing a CSS selector directly in the @font-your-face interface.
- The @font-your-face code is designed for re-use, so other modules can both supply and read active and available font information.
- Fonts can be exported/imported using Features (7.x-2.x only)
- You can also import your own local fonts in all web formats: EOT, TTF, WOFF and SVG.
NOTE: This module *may* be deprecated in Drupal 7 !
Here's your reason, basically the theming changes in D7 mean the field theming gets bound a lot lot later in the process, so it's not possible to generate the output into a Textarea for you to edit - that said, it is possible that we can come at this from another angle and use tokens instead BUT it means what you see in contemplate admin page will be nothing at all similar to the output.
You can view more on taking this module forwards here http://drupal.org/node/1285558
The Content Template (a.k.a. ConTemplate) module allows modification of Drupal's teaser and body fields using administrator defined templates. These templates use PHP code and all of the node object variables are available for use in the template. An example node object is displayed and it is as simple as clicking on its properties to add them to the current template.
#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.
This module allows the admin account (user 1) to add fields, filters and sorts to views which use PHP code. It also supports additional accounts when the core PHP Filter module is enabled.
Service Links allow the users to share a web page in various social networks like bookmarking services, social blogs and similiar, providing an easy way to extend their number. Built on Drupal for Drupal doesn't include commercial advertising codes and don't require third part libraries.
The services included are various: del.icio.us, Digg/Digg button, Facebook/Facebook Share/Facebook Like, Furl, Google Bookmark/Google Plus One, IceRocket, LinkedIn/Linkedin button counter, MySpace, Newsvine, Reddit, StumbleUpon, Technorati, Twitter/Twitter widget, Yahoo Bookmark, and many more, they are split for language in different packages: basque, dutch, farsi, german, hungarian, italian, russian, spanish, swedish.
Other services are availables as an extra module fully customizable with some click.
Provides integration between for the Plupload widget to upload multiple files and Drupal. Plupload is a GPL licensed multiple file uploading tool that can present widgets in Flash, Gears, HTML 5, Silverlight, BrowserPlus, and HTML4 depending on the capabilities of the client computer.
In order to protect your site you should ALWAYS delete examples subfolder from Plupload library. There is a patch, that can help you to do that in one simple step or to include it in a distribution.
Drupal 7 version
Drupal 7 version provides integration between Drupal and Plupload library via form element. You only need the 7.x version if another module tells you to download it.
This version is actively maintained.
Drupal 6 version
The current code is somewhat of a proof of concept that does a very simple thing: a single setting page, a single upload page, and content goes into an imagefield on a single content type using the HTML5 or HTML4 widgets. It creates one node per image. It assumes your allowed file extensions jpg,gif,png,jpeg.
D6 version is currently not maintained. We will only commit patches marked as RTBC. Feel free to contact module maintainer if willing to help.
The easiest end-user solution for resizing inline images.
This filter makes it easy to resize images, especially when combined with a WYSIWYG editor such as tinyMCE or CKeditor. Users never have to worry about scaling image sizes again, just insert an image and set it's height and width properties in HTML (this is done automatically by WYSIWYG editors) and the image is resized on output to match the HTML.
- Automatically resizes both local and (optionally) remote images.
- Optionally create a link to full size images from the resized inline versions.
- Prevents inline "hot linking" of images from other sites by storing them locally.
- Adds height and width attributes to inline images when your users are too lazy to add them.
The "resize handles" typically shown in WYSIWYGs do NOT work in Webkit-based browsers (which includes Safari and Chrome) due to a shortcoming in the implementation of these browsers. See https://bugs.webkit.org/show_bug.cgi?id=12250 and this issue for discussion: #1102294: Webkit-based browsers (Safari/Chrome) do not support resize handles.
The Frequently Asked Questions (faq) module allows users, with appropriate permissions, to create question and answer pairs which they want displayed on the 'faq' page. The 'faq' page is automatically generated from the FAQ nodes configured. Basic Views layouts are also provided and can be customised via the Views UI (rather than via the module settings page).
Meta tags support for Drupal 7 sites based on Fields API.
Pathologic is an input filter which can correct paths in links and images in your Drupal content in situations which would otherwise cause them to “break;” for example, if the URL of the site changes, or the content was moved to a different server. Pathologic can also solve the problem of missing images and broken links in your site’s RSS feeds. See more example use cases on the documentation page.
Enable users to create and manage their own 'groups'. Each group can have subscribers, and maintains a group home page where subscribers communicate amongst themselves.
The File (Field) Paths module extends the default functionality of Drupal's core Upload module, the FileField module and many other File Upload modules by adding the ability to use node tokens in destination paths and filenames.
In simple terms, File (Field) Paths allows you to automatically sort and rename your uploaded files using token based replacement patterns to maintain a nice clean filesystem.
- Configurable file paths now use node tokens instead of user tokens.
- Configurable filenames.
- Support for:
- File path and filename cleanup options:
- Filter out words and punctuation by taking advantage of the Pathauto module.
- Convert unicode characters into US-ASCII with the Transliteration module.
- Automatically updates unprocessed file paths in the node body, teaser and CCK text fields on save.
- Retroactive updates - rename and/or move previously uploaded files (Use with caution)
- [D6] Active updating - actively rename and/or move previously uploaded files (Use with caution)
Drupal Commerce is used to build eCommerce websites and applications of all sizes. At its core it is lean and mean, enforcing strict development standards and leveraging the greatest features of Drupal 7 and major modules like Views and Rules for maximum flexibility.
Whereas eCommerce solutions are often developed with an application mindset, highlighting what you can do with it out of the box, Drupal Commerce was developed with a framework mindset, focusing on what you can build with it. The core Commerce systems make no hard-coded assumptions about your business model, privileging developers and site builders at the core level to build custom eCommerce solutions to suit.
Sponsored by Commerce Guys