Minimally maintained

Generic helper module to allow external resources such as CSS, JavaScript and images to be fetched and cached locally.

This is the d7 sandbox port of the PET module

Integration with the odesk API. You must download the api php file and place it in your libraries directory. For example sites/all/libraries/odesk/oDeskAPI.lib.php

This project provides a CCK display formatter which shows all the past revisions of a file that were previously attached to the node, using core Drupal's revision system.

This module provides several theme functions which can be overridden and customized by renaming and copying to your theme's template.php file.

Instructions for use
Add a filefield to a content type at admin/content/node-type/node_type_name/fields and enable revisions at admin/content/node-type/node_type_name. Then, enable this formatter on your content type's field display settings at admin/content/node-type/node_type_name/display, called "File Revisions."

Behavior:
Add a file to a filefield. Save the node with the "create new revision" checked. Now, edit the node, delete the file from the filefield, and add a new file, with "create new revision" checked. The filefield set to display as File Revisions will now display the old file, as well as any other previously deleted versions of the file. To remove a file from this field, use the "Revisions" tab on the node and delete all revisions that contain the file you wish removed.

Requirements:
Drupal core revisions module
CCK
Filefield

Known bug

This provides chado feature specific export functionality to views data export.

This module was designed to solve the specific problem of rebuilding the node access table quickly.
This task would sometimes take the standard Drupal system tens of hours on sites with hundreds of thousands of nodes. Add to this, the fact that the standard drupal node access rebuild removes all access entries before rebuilding, and this can cause a site to be unavailable for many hours if the permissions have to be rebuilt.

The principle of this module is that this process can be sped up by making multiple simultaneous javascript calls to a rebuild script, which processes mutliples nodes at a time.
By adjusting the javascript request interval and the number of nodes to process per request, the module can be tuned for a specific site to make enough concurrent requests to provide a significant speed boost over serial processing, while not overloading the server.
Like the built-in drupal rebuild, the browser page must be left open during the rebuild, as the progress to completion is handled by client-side javascript.

The module works by returning a count of nodes (possibly matching a set of optional filters), calculating the highest and lowest node id within that set, then calculating the range between these. It then divides this range into blocks of node ids, according to the number per block setting on the administration page.