Maintenance fixes only

About

The goal of this project is to cleanly extend Apache Solr Search to provide:

• better support for non-English languages
• support for multilingual search
• cross-language information retrieval (CLIR)
• an easy-to-use administration interface

Apache Solr Multilingual does not replace Apache Solr Search but is based on it.

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:

1. Execution of views from a rule. The rendered results of this view can then be used later to pop in an email or add to a comment, etc.
2. Execution of rules by rendering a view - Via a new display type for views: 'Rules Executor', instead of rendering the results of the view into HTML we render the results 'into' the Rules module. You can specify a rule set to render each row into, and use the fields from the view to specify the arguments for the rule set.

This gives an incredible amount of flexibility and power, with this module you can do things such as:

• Automatically close issue tracker cases after two weeks of inactivity.
• Email users a digest of their new content every week.
• Disable comments on content over 2 weeks old.

Requirements

• Rules module.
• Views module - at least version 2.7 is required.

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.

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.

Requirements

1. Install Libraries module (D5 version has a "safe" backport embedded): http://drupal.org/project/libraries
2. Download YAML library from: http://code.google.com/p/spyc/
   Extract zip file and install spyc.php under "spyc" sub-folder of sites/all/libraries (or sites/sitename/libraries).

Also, please make sure to read README.txt accompanying the module, for installation and configuration instructions.

Maturity Status

Both client and server modules of the framework have been thoroughly tested in development and have no known issues. However, these modules are new, and have been used in production, only for a limited duration.

Credits

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.

This module is part of a package of modules being developed by Jefferson Institute. These modules are meant to serve as tools for data visualization:

• VIDI - Vidi module serves as a guide to choose adequate visualizations from Timeline, Tagmap and GVS modules for specific data, i.e. wizard with visualizations preview.
• Tagmap - Display a geo-coded tag cloud over Google Map. Taxonomy terms or imported external data can be displayed.
• KML content type - Users can attach .kml files to a node (with upload module), which in turn is displayed through the Google Earth API. If a user attaches several .kml files it is possible to choose between them via a drop-down box.

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.