Minimally maintained

Expires rows from the session table older than a certain time.

Background

By default, Drupal ships with a session expiration time of just over 23 days, using this directive in settings.php:

ini_set('session.cookie_lifetime',  2000000);

However, for this to work automatically, it requires PHP's garbage collection to be configured correctly.

Since some distributions, e.g. Debian and Ubuntu do not ship with PHP defaults that triggers PHP garbage collection, there is a need to also set the following:

ini_set('session.gc_probability', 1);
ini_set('session.gc_divisor', 100);

This will work, but has some drawbacks:

• It will be triggered at some random time, rather than at a predictable time.
• It could slow the response for the unlucky user who happens to trigger it.

So, on sites with a distribution that is not setup as above, or on really busy sites, the sessions table can grow to be very large, and that can cause slow accesses to it, as well as slow writes due to locking, leading to performance bottlenecks.

Single Login is a session management system for Drupal. It allows the site administrator to create a policy to detect, and prevent, duplicate logins on the same account. This is obviously handy for a site that requires paid subscriptions. Once a duplicate login is detected from a different system, the first login gets logged out. The admin can set a policy that determines how often and within what time period a session can "ping pong" between machines. Should the policy conditions be met, the admin can specify an action,typically to block the offending account.

Signatures for Forums tweaks signatures in ways inspired by other traditional forum software.

1. when a user changes their signature, all their posts will be updated;
2. signatures are automatically added to posts, instead of being inserted into the post text;
3. the administrator can choose the input filter for signatures, allowing BBCode -- if the BBCode module is installed -- or HTML to be used;
4. signatures are longer than the the Drupal default
5. conditional signatures, these are hidden, or rel=nofollow'd if a post is under a particular length;
6. show signature only once per conversation;

This module was developed for The Webmaster Forums (who have recently moved to Drupal--yes, we do like Drupal's forum!)

This module integrates the Zoomify applet into Drupal. Zoomify is a Flash applet that displays large images by allowing to pan and zoom into them. Images are first preprocessed in order for Zoomify to work.

The netFORUM Views module relies on the netFORUM xWeb Interface and netFORUM Dynamic Facade Nodes modules to pull a list of objects from a netFORUM database and present them as a page or a block, much like the Views module. It uses the same syntax as the netFORUM Dynamic Facade Nodes module, which is the same as Correspondence Templates in the e-Marketing module of iWeb, including conditional statements.

The Role Contact module creates a "staff list" from the profiles of users in a particular role, e.g. "staff role". The user list is formatted via theme functions, with convenient header and footer fields. The sort order of users can be set via weights. A configurable subset of profile data is shown in the user list view, along with the user's picture along with a link to a per-user page, showing a (potentially different) subset of profile data.

OG Contact provides a contact module style contact form for Organic Groups, and optionally provides a "Contact" tab on the group's main page.

Features

The PAM Auth module is based vaguely on a skeleton of the IMAP Auth module (http://drupal.org/project/imap_auth). It accomplishes the same goal except that it uses the PHP5-PAM module to accomplish the authentication. It also borrows some ideas from the ldap_integration (http://drupal.org/node/15109) module for password-form adjustments.

Note: As of 2012/03/12, this module is supported by new maintainer. As the previous module maintainer feel this message has been posted in error, please reply to #1466128: Offering to maintain bitcache module.

Bitcache is a distributed content-addressable storage (CAS) system. It provides repository storage for bitstreams (colloquially known as blobs) of any length, each uniquely identified and addressed by a digital fingerprint derived through a secure cryptographic hash algorithm.

This is a module that provides a Bitcache-compatible data storage repository for Drupal and implements the Bitcache REST API for interoperability with the standalone Bitcache command-line and synchronization tools. The Drupal module includes storage adapters for the file system and for MySQL, PostgreSQL, SQLite and GDBM databases, with Amazon S3 support in the works.

This module is an add-on to the FAQ module that allows users with the new 'ask question' permission to create a question which will be queued for an 'expert' to answer.

For more about why this module exists, please read "Ask the Expert" or Advice Column.

Viewing of the completed question and answer pair is done by the FAQ module.