Actively maintained

The CouchDB module provides API access to any Couch Database. The API exposes a majority of the Database, Document, Design and Views API. The CouchDB module when enabled does not do anything. It provides a library to build additional functionality or applications.

The couchdb_watchdog module is a sample implementation of using Drupal with CouchDB.

Please help solidify the development release into a full 7.x release by logging issues and testing the module out.

This module generates graphical representation of userpoints history, so users could see plotted their points evolution in time.

This module is currently in design stage and code will be unestable, so if your are not going to help or develop on it, please don't use it yet.

RTSG will make extensive use of this module (it was originally created as part of rtsg but published earlier because of a comment in a group), so the development status has been reactivated.

Media: Archive leverages the Media module and its media management framework including WYSIWYG integration. The D7 branch is still very much in development, but works for browsers that support the HTML5 video tag with Ogg or MPEG4. Yeah iOS support for video! Sorry IE6 and audio users :( Eventually IE6 users will see the Archive.org Flowplayer for video. We're still trying to figure out audio as well as PDF, images, and other content types Archive.org and Media both support. There is currently no upgrade path from emfield to Media.

This module enables Drupal to receive email messages and post them directly into a forum. Each forum gets its own unique email address, which only users registered on the site and assigned the permission "post by femail", may post to. For example, a forum titled "Femail issues" on this website would get the email address femail-issues@drupal.org. Users are able to subscribe to "All forums", or any number of individual forums. Once subscribed, any messages that they didn't post to the forum themselves will be emailed to them. If a user replies to these messages, they will automatically get posted into the correct thread within the forum, and will also be nested correctly. Email headers are also correctly set, meaning that a user using an email client that supports threading (Kmail, Evolution, Thunderbird, etc) will see the same message structure in their client as is seen on the website.

Data module helps you model, manage and query related sets of tables. It offers an administration interface and a low level API for manipulating tables and accessing their contents. Data module provides Views integration for displaying table data and Drupal search integration for searching table content.

You can use Feeds to import RSS, Atom, CSV or OPML files into data tables.

Lets the users of a Drupal site chat via a RealChat server. It adds a single link to Drupal's menu system called "Chat now!" by default. An authenticated user who clicks this link enters a chat at a designated RealChat server with her chat nickname set to her Drupal username, chat profile pointing to her user profile page on the Drupal site, and avatar set to her picture (if available) on the Drupal site.

This Module is Upgraded version (D7) of https://www.drupal.org/project/background (D6).

Its allows to upload a background image in appearance menu.

This works best in themes with fixed width and having no any other background image/color, where a background shows.

After enabling this module, Background menu will show under the Appearance Menu ..

This module adds the ability for site admins to add "Markup" widgets to the form. These essentially let designers of cck content-types insert additional markup into the node/edit form to display to content-authors. This is the equivalent of adding additional elements to $form of the type '#markup'.

The module does not add anything to the $node object for the content being created, and utilizes form_alter to remove unnecessary fields from the '_content_admin_field' form when this widget is being created.

Description

The Publication Date module adds a "Published on" date for each node, containing the date when it was first published.

Without this, the only dates available for nodes are their created date and changed date, but these are often insufficient to meet the needs of publishing workflows. Sorting nodes by their created date doesn't account for content which is held in draft form for a time while being readied for publication. Sorting nodes by their changed date fails to account for content needing minor corrections after being published.

This simple module add a contact form right under the node. You can choose:

• to add a contact form on teaser,
• to add a contact form on full view,
• to add a contact link on teaser,
• to add a contact link on full view,
• which content types these settings will apply to.

This check if user has rights to access contact forms.
It needs Contact module.