Under active development

Field Boxes proves a box type (see Boxes that allows for any field on any entity to be presented a a block).

Signup Node Spawn allows you to automate the copy-based creation of new signup nodes based on existing nodes. If you turn spawning on for a signup node, when signups close, a new copy of the node will be created, including the spawn settings. Spawning will be turned off on the original. This allows for continuous ongoing creation of signup nodes when seating limits close. You can turn off spawning at any time.

Background: This functionality was created for a Drupal platform that uses Signup to manage access to online courses with limitations on the number of students they seat. Signup Node Spawn allows us to automatically close and open new copies of courses when the limits are met. The module has been created with the potential for other applications, however. Please let us know how you use it.

INSTALLATION:
Install the module as usual, see http://drupal.org/node/70151 for further information.

Note this, from the Signup module:
Signups close in 3 main cases: (1) it is a time-based node and the close-in-advance time has been reached (auto-close via cron); (2) the node has a signup limit and the limit is reached; (3) a signup administrator
manually closes signups.

IMPORTANT:

Webhooks are "user-defined HTTP callbacks". They are usually triggered by some event, such as pushing code to a repository or a comment being posted to a blog.

This is essentially a fork of Inline Form Errors (IFE) for Drupal 7, with the intention of developing a near-enough bug-free version ready for production sites running Drupal 7. Or something like that. This sandbox is intended for use by developers at ComputerMinds to work together on this, as a contribution to the real Inline Form Errors module - we don't really want to fork that module for own purposes! We'll probably build towards some patches that will be submitted to IFE's issue queue.

Instructions for getting IFE set up -

1. Enable the Inline Form Errors module
2. You will need to enable IFE for each form you want to use it with - at /admin/config/ife, add the relevant form_id(s) to the 'Form conversion' table at the bottom of the page (you can use the setting).

To get the form_id for a form, you can tick the 'Show form_ids on form' option on the IFE config page, save, and then visit the form you want to enable IFE on. If your user has the 'administer inline form errors' permission, the form_id will be printed out at the top of the form.

Drupal 6 Driver for IBM DB2 DataServer. This Driver provides an interface to IBM DB2 DataServer Version 9.7 and above.

Installation

Download and setup a web server(for example: Apache)

	Set up a Web server as per the configuration recommended by Drupal (http://drupal.org/requirements).

Download and install DB2

Download DB2 version 9.7 from http://www-01.ibm.com/software/data/db2/express/download.html?S_CMP=ECDD..., use the resources available in the link to get started with DB2.

Configure php for DB2

Follow the steps below for respective platforms
Linux Platforms
Download the latest pdo_ibm extension for db2 from http://pecl.php.net/package/PDO_IBM
Install pdo_ibm issuing the following commands from the downloaded tar
phpize --clean
phpize
./configure --with-pdo-ibm=/home/db2inst1/sqllib #sqllib directory will be present under you DB2 instance users home
make clean
make
make install

Windows platform
Use the php_pdo_ibm.dll shipped in your DB2 installation package(In case of requirement of different version of pdo_ibm.dll write to opendev@us.ibm.com,to get the appropriate dll ).
Place the php_pdo_ibm.dll in the php extensions directory

Common for all platforms
Add the below line in php.ini file
extension=php_pdo_ibm.dll.

This is a sandbox for a "huge" fork of commerce_addressbook.

Do not use this module as it still in a big development state, and it is really not stable.