Under active development

The basic idea is to provide a module that allows for designing of steps, e.g. for a registration process on a site with the flexibility to tie together different components. This will be achieved by providing node independent steps, which can be created, increased, decreased, reset and of course manipulated via an API-like approach, which means you may well put a simple PHP one liner in a block which provides for step increment as well as a target node to lead the user to upon clicking the link User Steps generates.

Dependencies so far:

Description

ePayment integration for the Drupal Commerce payment and checkout system.

Credits

Developed and maintained by amateescu @ Tremend Software Consulting

This module provides Benjamin Lupton's History.js as a library to Drupal 7 via the Libraries API. It provides a configuration page to manage which compatibility mode and implementation of History.js to use.

What is History.js?
From the project's creator:

This module allows the Apache Solr module to independently index any Media file resources attached to nodes so that you can perform a search just on file attachments.

The use case we built this module for was a client that had various documents and media files associated with their products and wanted to have a global search of these files independent of the products they are attached to.

This module is built for the 1.x branch of the Media module.

This module is pretty straightforward. It purges the varnish cache for your devcloud acquia hosting for an edited page. This way your anonymous visitors will see the most recent version.

This is a placeholder right now, but the code will be posted in the next few days.

The Search API Location module (7.x-2.x & 8.x-1.x branch) adds the possibility of location based searching to the Search API module.
Currently only Apache Solr is supported as the service class.

You can view a demo here for Drupal 7 and view a demo here for Drupal 8

Displays the "read more"-link only for selected content types.

Set the image quality per image style!

Through Image Toolkit, you can set the quality of images the Image module produces. But since Image Toolkit allows you to set only one global value, any image produced by Image module ends up in the same quality. If you want to have the highest-quality images in a photo gallery while having lower-quality images elsewhere, you are stuck.

Required by OpenAcaDept, the distribution for building academic department websites.

Problem solved:

If you intensively use icons for (C)RUD-Hyperlinks in very many views, it becomes very disturbing to edit these image in each view field as rewrite.
Especially if these images change later on, it's not big fun.
Views Node Options Icons solves this by providing icon field for these cases.

Description:

- Built for Views 2, might(!!) work for views 3, but not tested yet -