Actively maintained

Built off the commerce coupon module, this module creates a gift certificate product, which, when sold, creates a single use coupon code to redeem the certificate.

This module allows you to to do use your favorite hook_form_alter techniques using rules

Objective:
Provide site developers access to all the power of the hook_form_alter through rules so they can store business logic along side other rules.

Currently provides:

• An event rules_hook_alter
• A condition to check the form id (option for contains or exact match)
• An action to set a form element value using three parameters [name][key] = value
• An action to set a form element [name] = array(...)
• Works with commerce_stock: all actions are available from the add to cart validation event. Can be used to create additional form actions like 'download product image'

You can set multiple properties of a form elements using multiple actions like #markup, #weight & #default_value.

You can create new form elements or modify existing once

You can reference nested elements for fieldsets in the format of:
{fieldset}/{fieldset}/{form element}

Also check out Rules Forms Support for similar functionality.

The module allows images uploaded into an image field to be displayed using the excellent jQuery Cross Slide plugin.

Islandora is an open-source digital asset management framework designed to help institutions and organizations and their audiences collaboratively manage and discover digital assets using a best-pr

This project exists to test that releases on Drupal.org work after new code is deployed.

This module provides a field type in order to assign a "probability weight" to it.

A probability weight is a float number which indicates a weight... not a fixed weight as many other modules do, but a weight with certain degree of randomness in order to ensure desired content appears in the first places with some probability, but not always. This module allows Views module to sort content in that way.

It's very useful in marketing context, where some products are desired to be promoted, but not always, in order to avoid being annoying.

Many fields can be assigned to any entity type, so you can have not only a unique probability weight per content, but many as desired.

Other similar project is Random Weight, but there are many differences because the scope is totally different:

• The most important difference: there is no randomness control with Random Weight. Weights are assigned randomly. With Probabilistic Weight, you can define which entities are most likely to be in the top by assigning them a probability.
• Random Weight generates a weight randomly using cron. But then, the weight is always the same and the entities will be sort the same way, until the next cron runs. With Probabilistic Weight, query results will be different each time query is executed.