Actively maintained

Node Auto Term or NAT is a helper module used to facilitate node-node relationships through the use of the Taxonomy module; i.e. when a node is created, a taxonomy term is also created automatically using its title and body in any associated vocabularies. Other nodes can now be tagged with terms from these vocabularies thereby establishing node-node relationships.

For example, consider a site with two node types - product and image - and a vocabulary named Products which is associated with the image node type. When a NAT association is created between the product node type and the Products vocabulary, any product nodes created will automatically also trigger the creation of a term with the same title. Subsequently, when we create an image node, we can categorise the image under a term from the Products vocabulary thereby establishing a relationship between a product node and image nodes. Later on, using Views or the NAT module's API functions, we can load and display related image nodes while viewing product node.

This module also attempts to preserve hierarchical relationships - where possible - which is useful when creating node-node relationships within the same node type. Using the above example, we could have also allowed for product-product relationships which would facilitate sub-products and so on.

Testers, feature requests and patches welcome :)

The Taxonomy Filter module is designed to present an easy-to-use interface for narrowing down taxonomy listings to find topics that are tagged by multiple terms. This is helpful for sites that use multiple vocabularies to create a multi-faceted information architecture.

Prior to Drupal 7 (see note in the "Drupal 7.x version" section), the core Drupal taxonomy module has the ability to do this with the following URL format:

/taxonomy/term/x,y,z

which will display a listing of all nodes tagged with terms x, y and z. However, not many visitors to your site will be aware of this functionality.

The Taxonomy Filter module allows your users to enjoy this functionality without needing to know the URL syntax described above. It does this by displaying a block of links that reference multiple terms from one or more vocabularies. The vocabulary filters are defined in the module's configuration settings. There the site administrator can specify that a vocabulary be 'filtered' by one or more vocabularies. The arrangement of the links in the block can also be specified by selecting one of the four menu templates -- default, cloud, context and dynamic.

This module adds user reviews to specified node types, on multiple axes and with voting via the Voting API module (required).

The petition.module is a means of conducting online petitions and collecting signatory names in CiviCRM.

The Advanced Menu module builds upon the Core Menu module to provide additional menu features. These include:

Menu Blocks (7.x-1.1+)

Administrators can remove menu blocks from the block admin page. This allows you to completely disable inactive menus and clean up the block admin page.

Menu Admin by Role

Menus can be administered by users with designated roles. This allows entire menus to be managed by non-administrative users.

Menu Attributes

Adds an expiration date to menu items and disables those items when the expiration date has passed.

Sub-Menus with Menu Merge (7.x-1.3+)

Menus can now be merged into other menus. This allows users with the appropriate permission to add links to other menus which are then displayed as if there were a single menu.

Examples

Example One:

Create new role "News Manager"
Create new user "News Editor"
Create new menu "News Releases", Set "News Manager" as an editor for the menu.

When "News Editor" signs in they will see 'Administer', 'Site Building', 'Menus', 'News Releases' in the navigation menu and will be able to modify and update all items on the "News Releases" menu.

Example Two, Building on Example One:

A News Release (pdf) is published to the site and needs to come down at 3AM.

Description

This module allows you to move comments and nodes around.

You can either