Enterprise Rotator is a complete rotating banner solution. It is build as a feature with a content type for each banner item and all the pieces needed to make the rotating banner work. It should not be confused with modules like views_slideshow or viewscarousel.
Check out OpenEnterprise for a great distribution to install Enterprise Rotator.
This module has two (2) features:
The module allows you to select multiple vocabularies in a single field entity. In Hierarchical Select, you can only choose 1 vocabulary at a time. It still synced the terms selected in the taxonomy table so you can still use this in views.
You can install this module just for this use.
Poll Extras provides additional flexibility to the core poll module. Here's the specifics:
Using this module, administrator can integrate Drupal with LimeSurvey,an open source powerful feature packed survey tool, which gives the capability of importing users from Drupal to LimeSurvey and registered users of Drupal site can see the public active surveys in there dashboard and take them as well! Furthermore, grant some users the ability to create survey or manage templates(if you wish!) on the basis of Roles or on per user basis! This module will be very useful for those who need a nice website/blog with the power of survey management.
Drupal & Storify, two technologies, two amazing products, one Drupal module to link them.
Storify is a site which allows you to make stories using tweets, photos, videos, or other social related stuff. You can easily drag and drop these items into one place, to make a story. You can then re-order the elements to improve the stories flow, and include your own text.
Storypal is the module who links Storify and Drupal.
The Semantic Blocks module enables the easy selection and use of the newer HTML5 elements as wrappers for blocks within the admin interface.
This gives site builders the ability to chose the element that encloses a block rather than rely on the hard coded element in the block template. This is done in the block add / edit form. If no element has been selected in the UI for that block it will default to div.
Replaces administrative overview/listing pages with actual views for superior usability.
The problem using Drupal book module and book pages as wiki is, the book page module adds book outline form part and the book outline menu as node/x/outline to all node types. All the node types do not need to be part of a book/wiki page. So this is the awkward part. I had to develop an application that had a wiki as a part with blogs and events as other services.
This module provides an API to define dependencies between entities, and also a useful iterator class.
This project originated from the Deploy module, where it's used heavily, but were later separated out for better code separation and reusability between modules.
You construct the iterator with an array of entity IDs. Then, when iterating over the iterator you will get all entities AND their dependencies out in a sane order (i.e. dependencies first).
Scans all nodes for duplications of node titles and removes all but one.
By design, it only scans nodes for titles that are exact case-sensitive matches, including whitespace.
The one with the lowest ID is taken as the original, all others are queued for deletion.
Both the scanning (which finds all duplicates) and the actual deletion are performed via batch processing.
This *will* destroy content. Because that's what it does.
This sandbox will not be getting a full release. It's a one-off tool that has the potential for a lot of support headache for me (solving other folks unique mistakes), and as I've learned not to make this mistake again, I won't be actively testing it going forwards. Please look at "Remove Duplicates" for feature requests.
