Maintenance fixes only

This module is an add-on to the Support Ticketing system module.

It allows an administrator to define custom CCK-fields to the STS content type (support_ticket) and then control which fields to display for which Client.

You could for example have a Product support Client with fields for customer number and Product. In another client you might want to specify other fields that allows the user to enter information that you think is necessary to give the user the best possible support.

This module is obsolete as of Support module 6.x-1.4

If you are stuck using 6.x-1.3 this module still works, it is recommended to update if possible though

 

 

THIS MODULE IS NOT READY TO BE USED WITHOUT PATCH, PLEASE READ THIS FIRST

This module is an add-on to the Support Ticketing system module.

In order for this module to work you first have to patch the support module with the patch found in this post:
http://drupal.org/node/694264#comment-2660904

Paranoid Form Validator can be used to prevent security attacks (cross-site scripting, SQL injection) carried out by submitting forms with malicious data in some cases. It works by adding extra validation to forms and raising error if unsafe data were submitted in form fields.

Creates a drush command line interface for setting an environment for a site instance. Other modules may then change their logic depending upon the current active environment. The drush env-switch command also invokes a hook to allow each module to run additional required actions when switching environments.

Timeline Map was built as a Views 2 style plug-in.
It is based on Timemap.js project, so Timemap.js (from http://code.google.com/p/timemap/) has to be included in the module’s js directory.

It allows you to load one or more datasets onto both a map and a timeline simultaneously. Only items in the visible range of the timeline are displayed on the map. Timeline Map displays data represented in the timeline as markers on Google map.

Description

Need to add a list of admin OpenIDs to many websites and not lose sanity while maintaining that list across all servers? This module is for you.

You can still maintain arbitrary list of OpenIDs on each site, but the framework ensures a list of allowed and banned OpenIDs (for the "admin" user), in addition to the local list.

This tool is for Drupal service-providers that maintain many websites and need to give admin access to a number of people, across multiple websites, for maintenance and support purposes.

Integration between Privatemsg, Views and Views Bulk Operations. Allows to create lists of private messages using Views and also provides optional Privatemsg UI based on Views.

This module integrates two of the most powerful Drupal modules: Views and Rules.

It allows your rules to execute a view, and your views to execute rules.

Two sides of the coin

This module provides two major pieces of functionality:

A collection of views examples that can be turned on and used directly within views. You can use the views examples as-is on your site, or you can clone them and use them as a starting point for further customized views.

Although this module works, it will likely be rewritten as a features package in the future.

A collection of modules providing apis for integrating drupal with RRDtool, the round-robin
database tool, used for tracking time-series data. The rrdtool module provides apis for writing data to and generating graphs from round-robin databases. The rrdtool_monitors module provides apis for incrementing counters in a persistent, distributed data store (currently only memcache is supported). And the rrdtool_drupal module tracks statistics from Drupal's core apis.