Модули

CCK Extras is intended to demonstrate a variety of "novelty formatters" and "novelty widgets" for editing and displaying assorted CCK fields.

Implements Zimbra (www.zimbra.com) e-mail accounts provisioning.

This module allow user to say 'I love this page'
A list of lovers of that page is created.

The module provides:

What is it?

This module provides two ways of referencing relevant content. Both of these methods provide configuration to filter for specific content types and vocabularies, limit the maximum size of the result and provide some header text. The result on both cases are a list of nodes which the module considers most relevant based on the categorization of the current page. This is achieved by finding other nodes which are of one of the allowed types and have the most number of terms in common. The two methods are:

Blocks

This module will provide as many customisable blocks as a site administrator wants. Each block has its own settings for node type, vocabulary, maximum result size and otional header text. Blocks can appear on any page which causes terms to be loaded into Relevant Content. Usually this is any page which views a node (a node page or a view such as a taxonomy term list). Usually you only want a block to appear on a node page, however you may find situation where you want to place a block on a non-node page.

CCK (new)

The new CCK Field Type (available in both 1.3 releases for Drupal 5 & 6). This is a read-only field (much like Node Referrer) which allows the administrator to embed a field that is "display only" (ie, nothing appears on individual node edit forms). This field is configured in the same way the blocks are configured; node type & vocabulary filtering, maximum result size limit and header text. The advantage of the CCK method is the result set is more "embedded" within the content.

This module allows users to write a letter to newspaper editors.

This module display a adjustable text size changer or a zoom function on the page for a better web accessibility.

The zoom function is comparable to the text zoom function in Firefox 3, but this module resize also variable media objects, variable pixel images and vector images. No JavaScript required (WCAG/BITV 6.3).

WCAG and BITV conform. Keep the conditions 1.1, 3.1, 6.3, 11.1 and 13.6. More Information: Web Content Accessibility Guidelines.

This module provides an API for Drupal menu display modules. By itself, it only supports drupal's default menus, so you should probably only install it if another module tells you to.

The Role Contact module creates a "staff list" from the profiles of users in a particular role, e.g. "staff role".

This is a custom search module for users. It provides a search page that can search for users by username, email, or a custom text field.

Visitors find your site with a search engine. Are you interested in what they were searching for?

Search Engine Referers is a simple module to view the search engine queries used by your visitors. It parses the referer URLs of popular search engines in you access log and extracts the search queries. Currently supported: Google, Yahoo!, Live.com, Yandex.ru, Rambler.ru.

** Looking for Co-Maintainer of this module. Someone who keeps up with changes to CTools module. **

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 simple module allows you to add a excerpt of latex to a content type.

The Slidebox module provides a JavaScript-based "Slidebox" - a box which provides a link to the next page in a sequence, which slides out when the user reaches the bottom of the current post.

Journal module adds additional fields to all forms in a Drupal site to allow developers and site administrators to record and track all changes that have been performed to setup a site or alter its configuration. Journal also allows developers to maintain a log of applied patches and customizations on a Drupal site, including links to issue trackers like Drupal.org issue queues (starting from 6.x-1.3 / 5.x-1.5).

Journal is primarily useful for developers and site administrators working in a team environment. Since Drupal is a fully-fledged content management framework, it is often not easy to communicate, track and audit all changes that have been applied to a site. Even without contributed modules one is able to build a totally customized site.

Maintaining a log of patches and customizations helps in determining whether a module can be safely updated, and moreover in building sustainable, well-documented Drupal sites.

Journal's log is comparable to the watchdog log in Drupal core. However, watchdog logs can be truncated or emptied at any time, so one would loose all entries.

This module allows an existing bricolage managed website to incorporate Drupal managed content into its pages.

This module extends the Primary menus with an additional level of secondary nice menus that hide/show on hover via jquery. Some theming is required to enable it.

WCAG and BITV conform. Keep the conditions 1.1, 3.1, 6.3, 11.1 and 13.6. More Information: Web Content Accessibility Guidelines or bundesrecht.juris.de.

The netFORUM Dynamic Facade Nodes module relies on the netFORUM xWeb Interface module and allows Objects from a netFORUM database to

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.