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 is an API module which lets you put several forms into one
The Front Page module allows for customised home pages dependant on role. The pages can be of the following types:
- Alias (only 2.x branch) - Allows for another Drupal path to be shown as the home page without redirecting the user.
- Redirect - Allows you to redirect users to a local or remote URL.
- Themed - Allows you to enter some static text that will be placed into the content area of a standard Drupal page.
- Full - Allows for static content to be displayed to the screen as is. This method does not pass through Drupal's theming system.
This is a Messaging Framework to allow message sending in a channel independent way. It will provide a common API for message composition and sending while allowing plug-ins for multiple messaging methods.
When using this framework, you won't send e-mails to users anymore. You will send them 'messages' and they will decide how they want to get them delivered, that may be by mail, IM, SMS, depending on user's preferences...
Drupal 7 upgrade
Some limited funcionality has been upgraded.
Development is back on Drupal git repository.
Author Pane is a block of information about a given user, like those typically found on a forum post, but can be used in other places as well. From core, it collects the user picture, name, join date, online status, contact link, and profile information. In addition, any module or theme can feed it more information via the preprocess system. All of this information is then gathered and displayed using a template file.
This module handles a very simple functionality, decide whatever to exclude a node title from full node page or node teasers.
It provides a checkbox on node-edit pages for easier exclusion, or you can use the admin page to manually enter a list of node id's to exclude title.
Also provides the option to hide all titles of a certain Content type. From the administrative interface you can select a content type to hide title for.
Use case: Let's say you create a content type called: Lightbox content, and in your layout lightbox content will have titles set on title attribute of the link, rather than inline on your page, so you would like to exclude title from displaying inline for all your nodes of type Lightbox content, simple, just check the option and voila.
How it works?
This project has some other, very simple approaches, like hiding the title from CSS using display: none or applying the template_preprocess_page hook in your theme to make the title variable null.
Actually Exclude Node Title does the same thing, only that you don't have to manually make different hacks, hard to track from the administration interface.
New features 7.x-1.5
This group of modules is sort of a recipe module that makes things easier by showing how to integrate some other modules as well as providing miscellaneous features that aren't distributed by Views itself. Sometimes these modules are only base recipes that will need to be themed and spiced up to fit your needs so be creative!
D8CX: I pledge that EVA will have a full Drupal 8 release on the day that Drupal 8 is released
"Eva" is short for "Entity Views Attachment;" it provides a Views display plugin that allows the output of a View to be attached to the content of any Drupal entity. The body of a node or comment, the profile of a user account, or the listing page for a Taxonomy term are all examples of entity content.
The placement of the view in the entity's content can be reordered on the "Field Display" administration page for that entity, like other fields added using the Field UI module.
In addition, the unique ID of the entity the view is attached to -- as well as any tokens generated from that entity -- can be passed in as arguments to the view. For example, you might make a View that displays posts with an 'Author ID' argument, then use Eva to attach the view to the User entity type. When a user profile is displayed, the User's ID will be passed in as the argument to the view magically.
That's right: magically.
Need some help?
DraggableViews makes rows of a view "draggable" which means that they can be rearranged by Drag'n'Drop.
This branch is complete rewrite of the module and uses field form http://drupal.org/node/769322 Views functionality. So now we can build our draggableviews with adding field. In first instance this branch won't support building tree structure. Only dragging items for reordering. 7
.x-2.x doesn't have upgrade path from 7.x-1.x so please completely uninstall 7.x-1.x version before installing 7.x-2.x.
This module allows users to export nodes and then import it into another Drupal installation, or on the same site.
Using this module you can save yourself a lot of time setting up new websites that have similar nodes to websites you've already made, migrating nodes to new Drupal versions, or between development/staging/production sites.
You will need the same content types for the imports to work (unless using Feeds to import), and ideally relevant compatibility with fields, and modules.
The migrate module provides a flexible framework for migrating content into Drupal from other sources (e.g., when converting a web site from another CMS to Drupal). Out-of-the-box, support for creating core Drupal objects such as nodes, users, files, terms, and comments are included - it can easily be extended for migrating other kinds of content. Content is imported and rolled back using a bundled web interface (Migrate UI module) or included Drush commands (strongly recommended).
imagefield_crop provides a widget for cropping an image after upload.
When the user uploads an image, the image is presented inside a cropping area. A cropping box is shown inside, and the user can resize and move it. Upon clicking 'preview' or 'submit', the image is cropped and the result is saved instead of the original image.
- Seamless, intuitive cropping, almost like using a desktop photo editing app
- All major browsers supported
- Dynamic preview - you see how your crop will look like, in real time!
- Original image is saved for recropping.
- No matter what resolution the cropping area is, the original image is used for cropping (for highest quality)
- The sizes of the cropping area, cropping box and resulting image can be controlled by the administrator
Version 7.x-2.x is a fork of the 7.x-1.x branch and it introduces a new field type (as opposed to just a widget in 7.x-1.x), and is incompatible with 7.x-1.x at this moment, and there is no upgrade path.
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)
This module provides a framework for easily creating searches on any entity known to Drupal, using any kind of search engine. For site administrators, it is a great alternative to other search solutions, since it already incorporates facetting support and the ability to use the Views module for displaying search results, filters, etc. Also, with the Apache Solr integration, a high-performance search engine is available for this module.
Developers, on the other hand, will be impressed by the large flexibility and numerous ways of extension the module provides. Hence, the growing number of additional contrib modules (linked below), providing additional functionality or helping users customize some aspects of the search process.
There is a screencast available, showing off some of this project's features. (Note, however, that it doesn't represent the current development state – e.g., facets can now be used with the database search, too.)
What is "Video" module?
Video module allows you to upload video in any format, play video in any format, transcode video to H.246, Theora, VP8(Web compatible formats) using Zencoder or FFMPEG automatically creates video thumbnails, deliver videos from Cloud file systems, Mobile device compatibility. Very reliable API for converting videos and auto thumbnail, embed video to node body using WYSIWYG module (D7 only) and many more.
A standardized solution of integrating external applications with Drupal. Service callbacks may be used with multiple interfaces like REST, XMLRPC, JSON, JSON-RPC, SOAP, AMF, etc. This allows a Drupal site to provide web services via multiple interfaces while using the same callback code.
Since our documentation is somewhat lacking on drupal.org, you can watch this for a 1 hour overview of what services is and what it does. http://denver2012.drupal.org/program/sessions/services-inside-and-out
Why Use Google Charts?
There are many reasons to choose Google Chart API over other methods such as Flash or Flex charts.
- Lightweight, reliable, no need for server side libraries or additional modules
- Simple to extend and implement within the Drupal framework
- Memory friendly. Thanks Google for taking the hit ;)
An example using the 7.x version.
$chart = array(
'#chart_id' => 'test_chart',
'#title' => t('Servings'),
'#type' => CHART_TYPE_PIE_3D,
$chart['#data']['fruits'] = 3;
$chart['#data']['meats'] = 2;
$chart['#data']['dairy'] = 5;
echo theme('chart', array('chart' => $chart));
Define dependencies between fields based on their states and values.
Conditional Fields for Drupal 7 is an user interface to the new States API, plus the ability to modify fields appearance and behavior on certain conditions when viewing content.
Conditional Fields allows you to manage sets of dependencies between fields. When a field is “dependent”, it will only be available for editing and displayed if the state of the “dependee” field matches the right condition.
When editing a node (or any other entity type that supports fields, like users and categories), the dependent fields are dynamically modified with the States API.
You can, for example, define a custom “Article teaser" field that is shown only if a "Has teaser" checkbox is checked.
This module alters the default search box in many ways. If you need to have options available like in advanced search, but directly in the search box, this module is for you.
The module adds options to select: which content type(s) to search, which specific module search to use (node, help, user or any module that implements search), which taxonomy term to search in the results (by vocabulary).
There are also options to: change the default search box label, add a default text in the search box, add advanced search criteria, change the default submit button text, use an image instead of the submit button, change the order of all the elements, include some elements in a popup block, and a filter can be added to the results page.
Dynamic display block slideshows are mainly used to showcase featured content at a prominent place on the frontpage of the site in an attractive way. A featured content slideshow can contain e.g.: New articles, Most popular content, New products, Portfolios, Videos etc.
For more examples see: Demo site
For example commercial themes see: Themes site
For sites using ddblock see: Sites using ddblock
For installations, custom configurations and custom theme developments fill out the design requirements questionnaire to create an efficient workflow.
Support for the dynamic display block slideshow module is given on a daily basis.
- Please post support requests, feature request and bugs in the issue queue and not on the documentation pages.
- Give detailed descriptions of your issues, so I can help you better.
- Searching the issue queue (search on all issue) and the FAQ can give you direct answers.
Slideshow theme layouts
The dynamic display block slideshow module is supplemented with free and commercial slideshow theme layouts. Examples of free slideshow themes and the commercial slideshow themes can be found at themes.myalbums.biz. Free themes can be found at the download page.
How you can help?
Below are some examples how you can support the development of the module:
- Write a review on drupalmodules.com.
- Post bugs, patches in the issue queue.
- Review documentation and post issues in the issue queue.
- Review module code and post snippets of code in the forum to improve the module.
- Post your site as an Internet site using the dynamic display block module.
I need your time, efforts, feedback and support for the module.
The module is developed and maintained by Philip Blaauw.
I like to thank developers like Aaron Couch (helped with adding Image cache support to the module) and Josh Waihi (helped with reorganizing PHP setting declarations) for their interest and help with the module. I also appreciate the help of others who found bugs, made suggestions for improvements, made issues to improve the documentation and who made reviews of the module.
Support and development of the module is made possible by selling new custom theme layouts and by paid services like installations and customizations of slideshow solutions.
Future of the dynamic display block module.
The module will get a 1.0 release version of the current RC6 version which fixes bugs. A new 2.x dev version for drupal 6 will be created which will have new functionality like in the Drupal 7 version of the ddblock module and in the views_slideshow_ddblock module for drupal 6.
Drupal 7 development version is released, please help with testing. The module now uses field mapping of views fields to slideshow theme fields instead of preprocess functions. An extra prev/next pager is available in all slideshow themes, an example theme with a scrollable pager is added. The module makes now use of themed views data instead of raw views data. No preprocess function anymore.
For paid installation, configurations and customization of the module and slideshow themes, you can contact me via my contact form. I also do a wide range of drupal development, configurations and theming for Drupal sites.
There are several other Drupal slideshow / carousel / rotator / tab modules available. Have a look at this comparison to find out what suits you best.
The Facet API module allows site builders to easily create and manage faceted search interfaces. In addition to the UI components that come out of the box, themers and module developers can build their own widgets that can optionally be contributed back to Drupal.org. Facet API works with the core Search, Search API, and Apache Solr Search Integration modules (including Acquia Search) meaning that code and configuration can be reused as-is with the most popular search solutions available to Drupal. Refer to the documentation for more details.
How to Contribute
The autoload module is a utility module. It allows other modules to leverage PHP 5's class autoloading capabilities in a unified fashion. It does, naturally, require PHP 5.1.2 or later.
You do not need this module unless you are developing a module that makes use of classes or you are installing a module that depends on this one.
The 1.x branch uses a manual info-hook. The 2.x branch includes a backport of the Drupal 7 self-learning registry as well as the info hook for backward compatibility.
Because this functionality is already in Drupal 7 core, there will never be (or need to be) a Drupal 7 version of this module. Leveraging this module for Drupal 6 class-using modules, however, will make moving to Drupal 7 easier.
See the included README.txt file for information on how to use this module in your own modules.
NOTE: Remember to clear all caches in your module's hook_enable() if your module relies on autoload. Autoload information is cached and your class may not be found if the autoload cache is not cleared.
The share widget (AddToAny) module by Lockerz helps readers share, bookmark, and email your pages and articles (aka stories) using any service, such as Facebook, Twitter, Google+, StumbleUpon, and over 100 more sharing and social bookmarking sites. Services are updated automatically.
The sharing module comes with a customizable Smart Menu, which places the services visitors use at the top of the menu, based on each visitor's sharing preferences.
This module allows you to specify content type(s) as being a block. This allows the content managers of the site to edit the block text and title without having to access the block administration page. Users only need edit access to that node in order to edit it.
It is very handy to create a simple block content type and enable this content type for blocks and use these in place of the normal 'add block' functionality.
Now supports translatable content
If Content Translation is enabled, then only a single node block per translation set is exposed and the node from the translation set with the appropriate language is loaded into the block.
There are several other modules and approaches that allow nodes to be presented as a block. See a comparison at http://groups.drupal.org/node/93499
The Drupal 7 version of this module enables the use of view modes. This gives the user even greater control over customizing the output of the node block. Default view modes and links display can now be assigned per content type and then overridden at block/node level.
This module intends to become a repository for advanced form elements, that can be used by other developers. Feel free to add your special elements to the issue queue!
|Element||Module version(s)||Included in Drupal core?|
|HTML5 elements (url, email, search, tel, number, range)||6.x, 7.x||8.x+|
|HTML5 attributes (placeholder, pattern)||7.x||8.x+|
|Table Select||5.x, 6.x||7.x+|