Under active development

An API module that allows a developer to put their default views into individual plugin files which makes it easier to manage them.

You will only need this module if you are a developer or another module uses it to store default view definitions.

The module allows a developer to put default views into individual files which makes them easier to manage in a source code control system.

Let the hunt for hooks begin.

About

The hook hunter enables you to search the usage of hooks throughout your project.

Transforms a Webform in a full-featured Quizz.
Can define rules for various webform components to give points.
On submit, total score is calculated, and actions can be thrown depending defined conditions.

Work in Progress : the module is not usable yet !

Developed on Drupal 7 and Webform 3.x.

Webform Dynamic Recipients lets a select (dropdown) field on a Webform determine who receives emails about form submissions. Webform users have always had ways to do this, but it involved writing custom code or including email addresses in the web page itself. This module provides the same functionality without extra coding or exposing contact info.

For example, you can:

This module adds a dquarks content type to your Drupal site.
A dquarks can be a questionnaire, request form...
These can be used by visitor to make contact or to enable a more complex survey than polls provide.

Submissions from a dquarks are saved in a database table and can optionally be mailed to e-mail addresses upon submission.

This is a development sandbox that is a fork of the Entity Translation module. It is meant as a starting point to easier get going with the following patches:

This module provides a Sphinx backend for the Search API module.

Requirements

Requirements are:

• The Search API module, of course.
• An Sphinx server which can be individually configured.
• Version X of the Sphinx PHP Client.

Overview

This module aims at allowing users to subscribe to a site or part of a site. A subscription can have different types (bronze, silver, gold, etc) and also different statuses (pending, active, grace period, expired, cancelled) .

Each subscription type can define an optional length in days for subscriptions and also a grace period, in which subscriptions expire but are left active for a few more days, giving the user a longer time frame to renew his subscription.

This project defines a field type, allowing to integrate nodes with the "Directory based organisational layer". You may add access control to nodes with the module "Directory based access control (ACL)".

This project defines directory based access control to the "directory based organisational layer" module. This module can be enhanced by the module
"Directory based field".