This module validates a user's age at registration. The minimum age is configurable in an admin page, as is the name of your custom date of birth field.

I didn't test this module extensively, so be sure to test before using on a production site.

Update: this functionality is now part of devel.module

This module gives you a user friendly interface to edit the Drupal System Variables (found in the variables table). In 4.7 when you remove a module, it sometimes leaves all its settings behind in this table. If you want to do a clean install, this is not always ideal.

Currently this module only allows viewing of a nested variables list and deleting of elements or entire tree's.

I'd like to add editing and "backing up" to this module too.

Ecommerce payment module for Virtual Card Services (vcs.co.za) a ZAR credit card payment service.

FEATURES
========
Utilises the vcs FETCH & POST method for confirming payments. Allows for callbacks from vcs to update payment statuses. Statuses are changed as follows; canceled - if user cancels payment, failed - if payment service declined the credit card, payment received - if payment was successful and denied - if the PAM (Personal Authentication Message) failed which is a security feature provided by vcs.
The ec_credit_card table is also filled although this does not seem to be implemented on ecommerce at the time this module was published. The ec_credit_card table contains the reference numbers and reason messages. Watchdog logs are kept for auditing purposes including the txnid and reference for cross checking with vcs. The module also allows for cell phone number and message text to be included for payment confirmation by vcs. Response pages are customisable.

MODULE SPONSOR
==============
http://www.econsultant.co.za/

This is a pure API module, providing functions for interfacing with version control systems (VCS). In order to work, Version Control API needs at least one VCS backend module that provides the specific VCS's functionality.

In subdirectories, you can find three modules that extend the basic administration functionality of Version Control API with additional functionality:

• Commit Log displays a history of commits.
• Commit Restrictions grants or denies repository access based on path, branch or tag.
• Version Control Account Status requires users to submit motivation texts and meet approval of version control administrators before their VCS account is enabled.

At the moment, only a backend for CVS is available.

This module was created as part of the Google Summer of Code 2007 where it was mentored by AjK and dww. You can find further information on ideas and development in the original project the original project proposal and in the Version Control API category on groups.drupal.org where the progress of the project was documented.

This module allows users to submit videos to a drupal site.

Drupal 5.0 users: video module development version already works with Drupal 5.0.

This module allows users to type Vietnamese characters while creating or editing Drupal nodes or setting the site name or menu names or taxonomy names, etc. It incorporates AVIM (Advanced Vietnamese Input Method), which is a nice open-source javascript that does the actual encoding of Vietnamese characters. As of this writing, the module includes the latest version of AVIM.

Benefit

Using views, change the system theme for pages like node/123.

Example

You could use the garland theme for your site but the pushbutton theme for pages like node/123 that are authored by Administrators in the last ten days.

Nodes hold content. Views save queries. Wouldn't be great if a node could hold a saved query? Now it can. Viewfield is a CCK field module that allows administrators to put views directly into nodes. When creating a node, users can select from a list of views. When the node is displayed, the view is run and the content is inserted into the body of the node.

Views 模組提供了一個很有彈性的方式，讓網站管理者可以很容易地設計網站內容的呈現方式。它可以製做出網頁和區塊，並以表格、摘要、全文、RSS等方式來呈現。

舉例來說，Views 模組可以輕易滿足以下需求：

• 你喜歡預設的首頁呈現方式，但是想要用不同的方式來排序。
• 你喜歡預設的分類呈現方式，但是你需要不同的排序方式，例如按照字首順序。
• 你使用最新文章（/tracker），但是想要改成只顯示某種內容類型。
• 你想要在區塊裡呈現某個內容類型的 5 篇最新文章。
• 你想要提供一個未讀的討論區文章的區塊/網頁。
• 你想要有一個類似 MT/Wordpress 的每月彙整文章的連結區塊，連結到不同月份的文章列表。

The views module provides a flexible method for Drupal site designers to control how lists of content (nodes) are presented. Traditionally, Drupal has hard-coded most of this, particularly in how taxonomy and tracker lists are formatted.

This tool is essentially a smart query builder that, given enough information, can build the proper query, execute it, and display the results. It has four modes, plus a special mode, and provides an impressive amount of functionality from these modes.

Integrates the Actions module into Views by providing a field for each action. Similar to how there currently exists an "edit" and "delete" link in Views, that you can add as a field, you can now add a link to perform any action available through the Actions module. Some of the most useful actions to integrate into views are "Publish Node" and "Unpublish Node", which were the original reasons for creating this module. If you add these actions into your view, you have links with each node Views retrieves to perform those actions -- that is, to publish or unpublish your node.

Each action is fully permissioned, meaning that you can have one view allow different sets of actions based on the roles to which a user is assigned.

Development for this module was sponsored by Prometheus Labor and was performed by Danaus Media, LLC.

The views_alpha_pager is a simple module that implements an alphabet pager (A B C) instead of a numeric pager (1 2 3) for views. This module relies upon a reasonable alpha sort order defined in the view. When one is not defined, it reverts to the numeric pager.

This API allows for easy and automatic creation of UIs to handle passing arguments to views. It creates a mechanism other than the URI for modules to specify arguments in block and embedded views. Now, there is a standardized interface for allowing users to pre-select arguments to pass to embedded views. In admin/build/views, you can select how you want arguments to be passed to an embedded view. In a module that you write, you can build a form for selecting those values (with simply one function call), process the submission of that form (with simply one function call), and call up and assemble arguments to pass to your embedded views (with simply one function call).

Here are some examples of what we can accomplish* with this module:

• You can now easily create a block that lists a different set of nodes depending on the current node's taxonomy.
• You can shows an image from a photo gallery related to the active node.
• You can create a block that shows a list of nodes authored by the active node's author.
• You can show a block of recent posts the current user made within an organic group when it is viewed.
• You can create one view and use it to generate different content for many different blocks.
• And more.

This module is simply a grouping of plugins and default views for Views, making it easier to integrate things that may be useful to many people, but should not necessarily be distributed with Views itself.

The Views Bookmark module is a flexible bookmark system whose primary goal is to give all the control to the administrator. Using this module, the site administrator can provide an arbitrary number of 'bookmarks'.

This module adds simple calculations to a views table. Requires the views module.

The daterange module provides a programatic extension for date ranges that can be used by other module developers. It creates new filters for node times, 'Node: Created Time Between' and 'Node: Changed Time Between', as well as new date range filters for CCK date (but not datestamp) fields.

If jscalendar is installed and enabled the date fields are augmented with the jscalendar button for selecting a date.

The supported operators are 'Custom date range', 'Outside date range', 'Before', 'After', 'within the past week', 'within the past month',
'within the past 3 months', 'within the past year'. When the the operator doesn't need both input fields, JavaScript attempts to undisplay the unused fields.

The date fields understand the words 'today' and 'yesterday' and sutraction of days, months, or years.

The views_fastsearch module provides a faster functionally equivalent alternative to the views "Search: Index" filter. This search is considerably faster (than the search in views_search.inc), supports OR terms, exception terms, and sorting by score.

1. It is noticeably faster - 5-20x faster
2. defaults to AND terms, but supports the OR keyword
3. implements exception terms using the – prefix (i.e., “global warming –ocean” searches for nodes that include “global” and "warming" but do not include “ocean”)
4. implements a sort by the search word score, when there are multiple terms, it sums them up – this presents results where the search words are in the title or header tags higher up in the list

This module is also a proof of concept of a solution using alternative search SQL that could be used as a basis for a patch to core.

This module is undergoing active development. If you use the 5.x-dev version, please read the release notes.

The views_filterblock module basically moves the horizontal filter from the views page content area into a (vertical) block. This differs from the views block option which displays the view exposed filters AND a limited number of rows from views content. It themes the block using collapsible fieldsets rather than the table currently used by views, and it uses some logic to decide which fieldsets should be collapsed or not collapsed based on whether the filter form has a value.

Views Fusion allows one to fuse multiple views into one. So you can build fusioned views that display information that is stored in multiple nodes - useful for tabular views. It uses node relations for joining the appropriate nodes together.

Currently the views_fusion module needs the nodefamily module for getting the node relation information. However in future other node relation modules could also provide their data for views fusion as it is written generic.

There is also a patch for the CCK nodereference field, which adds support for views_fusion.

Dependencies:

• Views (at least version 1.6 or a development snaphot)
• Nodefamily (or another supported node relation module)

The Views Mail module provides a flexible method for sending messages to
lists of users created by the Views module. You can view the history of how this module came about here: http://drupal.org/node/134931

This module uses the Views Argument API to allow you to use one view to generate many different blocks. You create a new view, specifying some arguments (a default one is provided, with a Taxonomy: Term ID argument). Then add some new views_multiblock blocks to your site and in the block configuration page, you use the accompanying form (generated via the Views Argument API) to specify the arguments to pass to the view.

Since this module uses the Views Argument API to deal with the view arguments, you have the option of doing a number of creative things, such as having your block switch which nodes are shown based on the taxonomy of the current node, based on the current user and more.

You can:

• Create a block that shows a related photo for a current node, and that automatically switches which related photo is shown based on the taxonomy of the current node.
• Create a block that shows recent content created by the current user, and that automatically switches which content is shown in the block based on which user is looking at it.

Based on Views issue #115947. The module adds a filter to your Views which can dynamically select a set of nodes to include or exclude from your filter chain by way of PHP snippets. Now your views can be customized in whatever way you want, without being limited to the existing filters and without having to write a new filter for functionality you may only have to use once.

This module saves values selected by users for exposed Views filters. If you have a view with an exposed filter which provides a page, the user can go to that page, select what to filter on, and these selections will be saved when the user returns to the page.

Allows users to schedule views. A scheduled view can then be linked to any number of actons.

This module makes use of Views.module, Schedule.module and Actions.module

This module will create a View type of 'Slideshow' that will display nodes in a jquery slideshow in a single div. To configure global settings, or for instructions to override slideshow settings for an individual view, go to /admin/build/views/views_slideshow

Module sponsored by Fresno Metropolitan Museum and Advomatic.

Use the issues queue or contact winborn (at) advomatic (dot) com for questions or comments.

Enables the presentation of views through tabs.

Requires Tabs module, part of Javascript Tools, as well as views.

Adds three new View Type options to page and block views. All three display each node (piece of content) on a separate tab.

• Tabs - Fields. You need to define at least one field to use this option as it displays field information.
• Fields - Teaser List
• Fields - Full Nodes

By default the titles are drawn from full content (node) titles. Configure the module at Administer › Site configuration › Views Tabs to select a length to truncate titles for better display.

Implements a Views plugin that adds a "View Type" to the Views page and block named "Tagadelic" (in addition to "Teaser", "Full Page", etc...). When selected, the nodes returned by the view are themed as a "Tagadelic" block in the same vein as the tagadelic module. At least one vocabulary field should be added to the Field List.

Allows you to create a view that is the union of multiple "sub-views".

For example, you could make a view that gets all the events within a certain date range, plus all the sticky events, regardless of whether they are in the date range.

Also, you can optionally set it to grab only a certain number of results from each sub-view. You can also have it grab zero results from a sub-view if exposed filters are used.

Assign permissions to vocabularies by user role.

The core taxonomy system allows vocabularies to be assigned to node types. This module extends that by allowing the editing and/or display of the vocabulary to be controlled by user role. It attaches itself to the vocabulary add/edit form and gives the administrator three options for each role - (1) edit and view, (2) view only, and (3) none.

This module makes it possible to create a vocabulary for administrator purposes, hide this category from most users, and then use the category as a views filter.

Here are two use cases:

• a vocabulary that had the terms "special offers", "front page", "user advertisement", etc; this vocabulary could be used in various views to pull the tagged content into a particular block or page.
• a vocabulary that had the terms "editor post", "editor tagged", and "community post" and a role type of "editor" that was less than an admin, but had privilige to write editorial content (as opposed to unedited community content), but also had permission to tag community content as something that was propogated to higher visibility.

Enables the creation of pairs of content (e.g. French Word-Swahili Word) and an optional associated explanation for learning purposes.

Most useful when used in collaboration with a viewer module (e.g. Flashcard Module, Typecheck module)

This module provides additional themeing pathways for voodoo theme.

This project is an attempt to build a digg.com/reddit.com clone.

Voting Actions bridges the gap between VotingAPI based rating/voting systems, and Drupal's Actions module. Administrators can set up rule sets to be executed whenever content is voted on by a user. The rule's criteria will be checked against the contents' votes, and if they match, the rule set's actions will be executed.

Defines a Voting API field type for content.module.

Currently provides 4 types of voting fields:

• Choice: user chooses an item from a list to vote on. Poll-like.
• Score: users rate nodes. There can be a range of scores or a single score like +1
• Percent: users specify a percentage from 0 to 100 and the average is presented. Currently input is limited steps of 5%. A slider-type widget could replace this with finer granularity.
• Author Rating: node authors specify a single numeric rating.

The input/output of this module is currently very primitive. The form input and results output systems are likely to undergo serious revision in the near future to support all kinds of fancy voting widgets.

This module requires VotingAPI, which it uses for vote storage, calculations, and caching. It also of course requires the CCK module since it defines CCK field types.

WARNING: This module is EXPERIMENTAL. Use with extreme caution. For a more mature solution, take a look at fivestar module.