Seeking co-maintainer(s)

This is a simple module to let users store their location on the edit account page.

Menu customization in various ways

Betting system is a set of modules that can transform your Drupal site into betting shop. It's mainly designed for course betting.

For better extensibility is created with more modules. It also defines own hooks.
The core of the Betting system adds the following:

• allows administrators to define basic parts for betting
• brings two new content types: Abonents and Games. Without abonents it is not possible to create games. Abonents are players (teams) that attend a game (for example Manchester United in the English Premier League, or Roger Federer in tennis).
• users can bet on games, but only if they have points
• each Abonent and Game have to be in a sport (which are defined by the Taxonomy module)
• administrators can set many options (like eventualities) in the Settings of the Betting System

Betting system also contains other smaller modules for functionality extension.

• Betting system relation allows the creation of relationships between games (like a half in a soccer game)
• Betting system flexible eventualities allows administrators to create special kinds of games, that do not have attending of Abonets and administrator can type own eventuality of result.

New Maintainer

We're happy to announce that @aaronbauman is joining the team of maintainers for this module. Thank you Aaron for donating your time and skills.

About Webform Registration

Webform registration was born from the need to allow visitors to fill out a sweepstakes form that would submit values to Eloqua and also create a new user.

At the time the webform register module did not provide enough flexibility to meet our needs, namely to allow a form to have many different field names (used for Eloqua mapping) and still keep track of which fields held the values for email, username and password to be used for user registration.

How is this module different from webform register:

• Maximum webform integration and flexibility
• You can add and fully customize every field that will be used for registration.
• If you are in a hurry, just add en email field and this module will handle the rest via a very user friendly and intuitive interface.
• Only the email field (webform component) is required, all the other components can be either generated by this module or omitted depending on your needs.
• Optionally you can specify all the labels and descriptions for all five fields (components): email, username, password, password confirmation and email confirmation

Take if for a spin and see for your self, this module won't let you down.

Similar Modules:

The Sampler API allows modules to easily collect and store calculated pieces of data. It's designed primarily to assist in collection, storage, and display of metrics.

Modules provide the API with a metric to track (eg. 'Number of comments added to a node') a listing of objects to be tracked (for example, you may only want to track that for certain nodes) , a sampling strategy (eg. 'every 3 days'), and a method that returns the calculated values for the metric (eg. 'give me the values that you want to store for the period of January 1st midnight to January 4th midnight).

Based on the provided data, the framework:

• Performs calculations to determine the how to sample for the metric
• Calls the necessary functions to gather the calculated values
• Handles all storage of the metrics
• Provides default views of the metrics

Metrics are made available to the API via plugins, and are responsible for handling the calculations that the API tracks. This architecture allows for a large amount of flexibility in what can be collected and stored -- there are thousand of things that could be measured, and the API makes no attempt to decide which ones matter.