New Drupal Modules

Coming soon.

Adds a full-screen element to the page during build that hides the entire page until it is loaded, then gracefully fades away.

Code is being developed.
This project currently has no release.

This module aims to utilize a greate portion, if not all the potential of the excellent Jvectormap API.

What can this module do for me?
Jvectormap lets you map events, colors and other stuff to different parts of a SVG image. We span this with Forms API, FIeld API and Features API, and what do we get?

Exportable, reusable, editable, scalable and *really* cool Jvectors (not necessarily maps).
You can draw buildings, things, and even car parts, then import it. Single color 2D, but still.

Features:
- Create jvectors from any SVG code (only clean paths at the moment)
- Save them as entities
- Export them to Features
- Use them as replacements for select fields
- Entirely Field API compatible

This module provides simple ajax integration between the clientside_validation module and arbitrary validators
written for the webform_validation module. It does nothing on its own, and is intended only to
simplify the process of validating webform components via ajax.

Clientside Validation provides javascript implementations of many Webform Validation validators, and in general
this is far preferable to validating via ajax. However, there are some cases where validation must
be done on the server side (e.g. those involving web-services with private API keys). This module allows
you to perform those validations via ajax, seamlessly integrating them into an existing clientside
validation user experience.

Usage
Any Webform Validation validator can be "ajax-enabled" simply by adding an 'ajax' => TRUE key to to the array
returned by hook_webform_validation_validators(). For example, an existing validator could be enabled as:

  function mymodule_webform_validator_alter($validators) {
    $validators['the_one_to_enable'] += array('ajax' => TRUE);
  }

That's all you need to do. Once enabled, any components having a rule using that validator will be validated
via ajax, unless they are specifically excluded from clientside validation (via the checkbox on the component
edit orm).

Notes
- Components validated via ajax will be validated a second time when the form is actually submitted. If you wish
to avoid this, you must implement hook_webform_validation_validate() so that it only executes once -- for
example:

  function mymodule_webform_validation_validate($validator_name, $items, $components, $rule) {
    // Prevent this from running twice - once on ajax and then again on form submission.
    if (function_exists('_webform_ajax_validation_enabled') && _webform_ajax_validation_enabled('active_phone', $component) && $_GET['q'] !== 'webform_ajax_validation') return;
    ...
  }

Note that this will not be possible for existing validators.

Known Issues
- If you have more than one ajax validator on the same component, you cannot currently
set a different custom error message for each (this will hopefully be fixed in the future).

- If you have more than one component in the same form validated via ajax, there will be a
separate ajax call for each validation.

- Ajax calls are synchronous, so you cannot display a throbber.

[mailmime] sandbox

dreditor companion for use at http://core.drupalofficehours.org/

Install user script http://drupalcode.org/sandbox/valthebald/2000880.git/blob_plain/refs/hea...

This module enables Views integration for the Invoice project. Some basic fields are integrated, contributions are more than welcome.

This module enables you to define on which zoom level you should see what layers. This module was initially build to be used with the Google Maps base layer.

Usage

Enable the module and configure this on the Behavior tab of your map.

A proof-of-concept of how accessibility checking can work in Drupal. Eventually this project will have:

1. Accessibility - A core module that exposes APIs for checking against tests.
2. Accessible theming - A tool for theme developers to test their themes.
3. Accessible content - Similar to the Accessible content module. This will also support WYSIWYG integration.
4. Accessibility tests - Integration with TestSwarm for developers.
5. Accessibility reports - Data collection and reporting for failed accessibility tests in content.

This is a demo sandbox module for my test

Drupal module for regression site testing.
It's a monitoring tool which is notifying the webmaster about a new changes on the specific pages. These changes can be marked as regression or can be ignored for the future changes.

INSTALLATION

1. Download and install the module.
2. Regression module requires FineDiff library to work correctly. Please place its finediff-code.php file inside the sites/all/libraries/finediff folder.

USAGE

1. Open module configuration page.
2. Go into /admin/config/regression/paths.
3. Click "Add new path" button. You will be redirected to the page of path configurator.
4. Enter list of pages which should be included or excluded from regression testing. You may use '%' character to describe dynamic parameters.
For more details, please read README.md.

Technical notes

Regression entries are added for every unique page (identified using
predefined parameters(keys)). There is a configuration screen that precedes
adding a regression entry where we configure regression entry keys used to
identify uniqueness of page.

If you have found this module you have probably created a field with a max_length that is no longer valid. You are either unable to store a value since it exceeds max_length, or perhaps you want to shorten the max_length to reduce database size? The field API in Drupal 7 does not allow you to change this property when data is already stored for a field. When trying to edit the max_length property in the admin interface you will encounter the following message:

There is data for this field in the database. The field settings can no longer be changed.

Or perhaps you encountered the following issue while adding or updating field values programatically:

PDOException: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'X' at row X

There are multiple solutions here:

1. Drop all your data and modify the field max_lenght. Just kidding, this is not an option
2. Modifying the field tables manually in phpMyAdmin
3. Creating an update hook that alters the field tables
4. Installing this module and simply edit the max_length in the admin interface
5. Installing this module and run the Drush command to modify the max_length

I will expand this module page with more information about step 3 since it is a valid option. As you might understand i prefer you just download and use this module :)

Other modules
I have searched for similar modules but have only found the ones that will add validation. If you feel this module should not exists because there is a better alternative please let me know.

Commerce Pre-order provides a framework to allow pre-ordering products utilizing Drupal Commerce's checkout.

Sponsored by Nack Creative LLC

Features

• Special product pricing for pre-order period
• Automatic pending order creation to capture funds once the product is available

Architecture

This module creates a pre-order price and status field on every product type which is used to trigger special pricing of the product during the pre-order period. The future due amount is accounted via new orders created after checkout.

• Special product pricing for pre-order period
  • This module creates a pre-order price and status field on every product type
  • Pricing rules set the price to the pre-order price while the product's pre-order is enabled (ie status field)
• Automatic pending future orders creation for each pre-ordered line item
  • On checkout complete via rules, pending orders are created for each pre-ordered line item. The line items can be grouped by product type to create fewer pending orders.
  • Product type setting for 'combine order' is on the product type form provided by the product ui
  • Each new pending order is referenced to the initial checkout order via an entity reference field on the order

Health monitor is a great solution to monitor custom functionality built into your site.
The Health monitor module makes it easy to hook into, and add custom "monitors" that display status messages on an admin dashboard. Health monitor can automatically send e-mails when a monitor returns an error.

Adding a new monitor is simple, just create a hook: hook_health_monitors().
Return some info:

  $monitors['check_nodes'] = array(
    'name' => t('Check number of nodes'),
    'group' => t('Example Group'),
    'description' => t('Checks to make sure at least 1 node exists.'),
    'args' => array('threshold' => 1),
  );

This monitor will now call hook_health_monitor_MONITOR().
Your hook should return a status:

function health_health_monitor_check_nodes($args) {
  $count = get_node_count();
  if ($count >= $args['threshold']) {
    return array(
      'status' => HEALTH_OKAY,
      'message' => t('There are !count nodes in the database.', array("!count" => $count)),
    );
  }
  else {
    return array(
      'status' => HEALTH_ERROR,
      'message' => t('There are only !count nodes in the database!', array('!count' => $count)),
    );
  }
}

.... And you're done. Wasn't that easy?

Use case
It is a field formatter based on custom formatters module.
It is useful when you have users with a imagefield empty and you want to display an standard avatar (male or female) according the values of another field (sex field).

A standalone form for creating arbitrary payments with the payment module.

• Very useful for a webmaster who needs to log payments against users (sponsorships, taken cash, etc).
• Also good for donations.

Simple Bank Transfer payment method for Ubercart

Current Version:
- Multiple account from one single settings

Todo:
- Create capability to support multiple bank account
- Create bank transfer report page
- Create bank transfer confirmation page

This is an integration of Westpac's PayWay gateway as a method for the Payment module.

Currently it only handles PayWay Net (Not PayWay API).

Term Value provides a new compound field type allowing entry of term reference and textfield pairs. The use case for this is to use a vocabulary to define types of values that can be provided, leaving it up to the content author to choose what values are provided.

Widgets

Currently we only have a select list for term reference and textfield for value. This module could potentially support autocomplete term reference and textarea etc but not at the moment.

Formatters

There are three formatters provided, choose which one suits you best. In future additional settings may exist, such as linking the term reference to the term page.

• Separate fields: Attempts to render each term/value pair as if they were separate fields. Please report any issues that may arise with this formatter.
• Separate items: Very basic rendering of each item using the Form API item type.
• Table of term/value pairs: Terms on the left, values on the right. Some formatter settings could be useful here.

Views integration

Works well for separate items and table formatters. Not so well for separate
fields. Not sure it will be possible to provide decent filtering options either.

Tired looking at the boring batch page ? Always going for a walk when running simpletests until they are done ?

Add a video to it and have some fun while you wait! Videos are config entities, so you can easily create your own videos.

Inspired by Alex Pott during a Drupalcon breakfast.