New Drupal Modules

Objective

• Create a case tracker that maintains a history of various stages of product development.
• Create a graphical representation for comparison of current status with dates as promised by the e-Commerce store/artisan.

Description

• Make a case tracker to track various stages of product development throughout, from the customer to an e-Commerce store (in case of a commissioned product).
• Provide a timeline, that is, a graphical representation of a comparison of current status of the product with the pre-decided dates as promised by the e-Commerce store or by the artisan to the customer.

Benefits

• Ease for a customer to keep informed about the current track of the product - only the manufacturing status.
• Advantage for a customer to compare the efficiency of an e-commerce store or an artisan by looking at the graphical chart of the current status of product development with that of completion dates as promised by the store.

Functionality

• Dependency – The module is dependent on product module of Ubercart.
• After installing the module, set ubercart classes on which case tracker is to be allowed with an optional timeline feature.
• View case tracker after creating a node of the set ubercart class type.

Developed by : gauravjeet_singh, itsmebhupendra
Sponsored by : OSSCube

This module create a token type called 'views'. This token can be used to embed
your views into your content.

Prerequisites

• Token
• Views

You also need the token_filter module to enable toking replacing in your node fields if you wish to use these tokens in node fields like body f.ex.

Installation

To install, copy the token_views directory and all its contents to your modules
directory.
To enable this module, visit Administration -> Modules, and enable token_views.

Simple SSO is specifically designed for Drupal sites that need a simple, intuitive and functional SSO system. The Simple SSO module can securely log in users accross several Drupal sites without needing to redirect the user to a single login form. The user always uses the login form on the site he's currently on.

Quick setup

Simple SSO comes with 2 modules, Simple SSO Client and Simple SSO Server. One Drupal site must act as the Simple SSO Server. All other Drupal sites are SSO Clients.

Simple SSO will not automatically create new users on client sites. It's up to the site administrators to make sure all users are shared amongst their Drupal sites (like using a shared user table for a multisite install).

Simple SSO uses a private key for token encryption. This key must be shared across the entire network (clients and server). The key should be added to each sites settings.php file. At the end of the file, add

<?php
$conf['simple_sso_key'] = 'YOJlYpWSO4cDW8KnnKeOYImXysLJr6nBt7f07U0'; // The longer and more random, the better.
?>

Remember that the key must be the same for all sites (tip: you can store this key in a plain text file outside the webroot for more security. In that case, just do $conf['simple_sso_key'] = file_get_contents('/path/to/key.txt');).

For each client site, go to the settings page and set the address for the SSO Server site and you're good to go. Simple SSO will automatically start logging in users across your site network.

this modules add the goenames api to the geocoder using ctools.

This module will enhance the editor experience by providing a great menu for editors

Review Token provides a tokenised URL for bypassing access restrictions on unpublished content.

It can be used to provide per-node access for unpublished content to users without logins, though a specially crafted URL.

Currently incompatible with modules which provide workflowed versioning, as the module will load the current published content, rather than a specific draft.

This module was originally created by Boztek.

Sponsored by the Australian Government Department of Sustainability, Environment, Water, Population and Communities.

This modules provides an api and set of tools for creating flexible content types, taxonomy terms, and their respective fields and field groups. Although the base functionality is similar to what is offered by Features, these tools are entirely maintained in simple to create/edit/update yaml files with only as much information as is needed; there is no need to alter fields or content types in the UI and then recompile; just alter or add a setting in the code, rebuild the content type or taxonomy vocabulary, and you're done. When utilized to it's fullest potential, this module provides a code-based alternative to the Field UI.

This is a simple module that wraps around a php translation of the reddit api. Upon activation, Redditview creates a block that will pull in a set number of the most popular items from the users subreddit of choice, including the item title, preview thumb (if available - with link to original image), and a link to the comments associated with the subreddit item. The api can be extended much further to include commenting from drupal, upvote count, etc.

Once activated, this module creates a db table that is populated with:

1. Reddit Username
2. Reddit password
3. subreddit name
4. Number of posts to return

The form is found here: /redditview/form-fill

I intend to develop this module more and add features to include upvote count, commenting, as well as views integration, and js prettifying. Right now, I'm placing this rudimentary implementation to gauge interest in this project / module.

This module integrates with the liveDocx third party service for generating dynamic microsoft word and pdf documents. For templates this module uses a docx file, supplied by the user, with mail merge fields for variables. This module is currently under development and the initial proof of concept was sponsored by Forum One Communications.

Credit goes to Eric (Last Name?) and his blog post here for a great start to the proof of concept.

Road Map Items:
coming soon!

This is my personal version of Devel, which utilises Devel functions in a slightly different way.

It's main use is to provide an analogue to dpm(), xdump().

The key differences are:

• xdump() does not try to guess whether your data should use krumo or not, and this will properly differentiate between FALSE, 0 and NULL, and give you line numbers for text dumps
• xdump() can be used within batch processes or other places dpm() will turn itself off

Though patches are welcome this module is largely unsupported and may break at any time, but if you know what it does that probably wont bother you.

API

<?php
// Dump a variable to messages.
xdump($some_var, $name = NULL, $type = 'status');

// Dump using KrumoNG (if installed)
xkng($args);

// Dump using Kint (if installed)
xkint($data, $type = 'status');

// Export a human-readable CSV of all modules and their installed state.
//
// This should be called from devel/php, as it will spit out a CSV file.
xdevel_module_list_csv();
?>

This module will allow you change the view mode of an entity via Context module. A reaction will also be available.

(See #1221892: Context module integration)

Import or aggregate RedHen CRM data using Feeds.

Text Link Formatter allows you to link text fields in the field formatter settings with the link fields or with content. E.g. you have a content type teaser and a link field and you want to link the teaser to the entered link.
It is very similar to Linked Field module.

Also you can use other approaches:

• Custom Formatters
• Token formatters

This module adds new taxonomies tokens to use in your nodes, paths or breadcrumbs, for example, like [parent-term] and [parent-child]

Field formatter to display image fields on referenced nodes.

TBD

A set of tools to integrate Drupal with Open Simulator servers.

Current features:

• Opensim core, featuring a preference panes to set access to Opensim database
• Alternative grid info block, showing hypergrid active users as well as usual data (login URL, local accounts, active local accounts, regions).

Future features

• Show user owned regions / simulators
• Link payments to activation / deactivations of regions / simulators

Useful modules

• d4os: integration with Opensim, including user creatioon

Defines a Map media type and enables the embedding of various map types. Currently supports ArcGIS out of the box, but it can easily handle other embeddable resources.

Requires Media 2.x or greater.

Allows viewing of Watchdog messages for events triggered by users that have since been deleted.

Without this module the detail screen of those message events will appear blank.

See: http://drupal.org/node/7428

Is there another module that handles this? I am going to promote this to a full project but thought I would wait to see if there is another module first.

This will make your website pass gas when you scroll.
Just for novelty.