Actively maintained

EBS Payment gateway for drupal commerce.

Sandbox to develop bookmark.

Rules integration for Nodequeue module. Partly working module I started for a job I made can be found on github: https://github.com/omissis/nodequeue_rules

Premise

This module was created to address a couple of issues that made using/modifying UC Store Credit unattractive:

WhatPlayed enables collection and display of "play events" from one or more external sources. These events are probably music tracks being listened to on some device but could also be video clips, movies, etc. The module relies on 3rd party notification tools and audio/video player software to perform event notification via a URL POST. Currently two specific notification tools are supported:

This Module imports information from CafePress into database tables in your drupal site.

It uses Your own userID and password from Cafepress and the CafePress api for this. So you will need to apply for a Key. So to get a key follow the getting started on this webpage http://developer.cafepress.com/docs/Getting_Started .

This module does not format any way to view your cafepress products or storesections it only imports them into a database table for you.

******************************************************
WARNING: THIS MODULE IS NOT READY FOR PRODUCTION YET - IT IS STILL "IN DEVELOPMENT"
******************************************************

INTRODUCTION
------------

Current Maintainer: Ned

Drupal 6 module to send SMS Blasts to bulk lists of numbers.

Depends on SMS Framework.

Safety Pay integration for the Drupal Commerce payment and checkout system.

Last compatible check done with commerce 7.x-1.0-beta3.

This module is on development, please do not use it on production.

I have been trying to get a test account on safetypay for months(Nov2011-Feb2012) and it seems like they do not want to offer one.

resources:
http://terminal.jcubic.pl/

Monitor References is a simple module that makes the values for nodereference and userreference fields on a form as they are filled out on the form. What this means is that nodereference and userreference fields which use views to define which nodes can be selected can use another nodereference or userreference field's values as arguments for their views, provided that the value is given programmatically.

Usage case

For instance, say you have these for the source field's values: