Actively maintained

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.

Documentation
The dynamic display block slideshow module is supported by a complete set of documentation, like: Installation and configuration tutorials, Video tutorials, FAQ, How to's, Tips, etc.

Support
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 Maintainers

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.

Drupal 6

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
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.

Drupal 7 - Advanced slideshow tutorial at http://ddblock.myalbums.biz
This is a quick step by step tutorial, which assumes you have basic drupal knowledge.

Paid services
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.

Note:
There are several other Drupal slideshow / carousel / rotator / tab modules available. Have a look at this comparison to find out what suits you best.

This small module provides a simple API and should not be installed unless required by another module, or for your personal development.

Features

• Route XMLHttpRequests to mapped callbacks
• Option to gzip output
• Display status and error messages based on request status
• Message display duration
• Output messages to specific elements, or the default of #ac-messages
• Response headers
• Ability to alter responses via hook_js_response_alter()
• Lock arbitrary requests to a set duration

Examples

This example utilizes AC.request() to delete a piece of content.
The URI of example.com/js/example/delete will call example_js_delete().

       // example.js      
       AC.request('example', 'delete', { 'content_id' : 1 }, function(response){
          // AC.checkResponse() will return TRUE when the response was a success, and also manages 
          // functionality such as displaying messages.
          if (AC.checkResponse(response)){
            $('#content-1').remove();
          }
       });  


// example.module
function example_js_delete(&$state, $args) {
// Lock the user for 10 seconds regardless of success, to prevent arbitrary requests
$state['lock'] = 10;

Right now is being developed a new Drupal 7 version, support for xmlpipe2 and a better documentaiton.

This module integrates the Sphinx full-text search daemon with Drupal. Sphinx is a full-text search engine, distributed under GPL version 2. See more at http://sphinxsearch.com

Current features include:

• Simple and advanced search forms
• Excerpts
• Use and management of several indexes, and even more deamons
• Easy per index management of fields and attributes
• A local page for each index
• A search phrase spelling suggestion module using pspell
• Faceted Search - using MVA's and groupBy features
• Configurable paths

The module is aimed at enterprise scale Drupal sites with large amounts of content. The module is not plug and play. It integrates Sphinx and Drupal, but you need to know how to setup indexes with fields and attributes in order to use the module successfully.

This module is maintained by Nestor
Nestor (english blog)
Nestor (blog en español)

And sponsored by:

Overview

This module provides an implementation the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) for Drupal with support for CCK content types and their fields. By implementing the OAI2forCCK module, you can expose content (its metadata) as an OAI-PMH repository. It will then be accessible by OAI harvesters. For further OAI documentation, please see here: http://www.openarchives.org/OAI/openarchivesprotocol.html

Functionality:

• Receive OAI-PMH request of service providers in form of HTTP request (GET or POST)
• Handle and responsd to the OAI-PMH request
• Map Drupal nodes (created by CCK module) to OAI records (use the configuration on admin settings for oai2ForCCK)
• Respond to OAI-PMH request in form of HTTP response (XML) to the service provider

D6 branch

The D6 branch allows a user to select which content types they wish to expose in their OAI repository. After selecting the content types to expose, the user can specify fields from each content type to expose and assign them a tag like 'dc:subject', 'dc:creator', etc. The D6 version can currently respond to Identify, GetRecord, ListIdentifiers, ListMetadataFormats, and ListRecords requests. ListSets is currently not implemented (and not required by OAI).

"Album Photos" is an image album module providing multi-user album features. The module development objective is to provide a comprehensive image album solution for Drupal.

A very small module to make requests to http://example.com/favicon.ico forward to the actual site's true favicon.

This module takes the favicon for the current site/theme and makes it available at the url example.com/favicon.ico (where example.com is your domain). The problem is that some web browsers and web applications blindly make a call to example.com/favicon.ico looking for your sites favicon. In drupal this causes an error entry to show up in the logs because there is nothing there.

If you want your icon to show at that address you can put a copy of your favicon n the root drupal directory. But, what if you have a multisite configuration with different favicons. This module will allow that address to show the current themes favicon at example.com/favicon.ico and it will work for multisite configurations.

Configuration

For this module to work properly you need to:

1. Drupal 6: enable the core 'Shortcut' module
2. Drupal 6/7: comment out #RewriteCond %{REQUEST_URI} !=/favicon.ico in the Drupal root .htaccess file

Credits

Currently maintained by Deeson Online