Maintainers strive to actively monitor issues and respond in a timely manner.

Comment Delete

Advanced comment deletion rules with threaded replies handler. Adds the hard delete, partial hard delete, and soft delete handlers.

Menu Node API

The {menu_node} table

Manages relationships between node ids and menu items.

The Menu Node API project fills in one of the "missing tables" in Drupal. This module does nothing on its own. Instead, it creates and maintains a {menu_node} table. This table maps the relationship between a node and its menu item (if any).

The module requires the optional core Menu module to be enabled. It also requires Drupal 6.10 or higher. (See this issue for why).

By itself, this module has no end-user functionality. When nodes are assigned to a site menu, records are created to capture that relationship. If the node or menu item is deleted, the record is likewise deleted.

This process enables other modules (such as Views) to write JOINs against node items in the menu system.

Drupal 7 version

Patch #457450 made it into Drupal 7. The Drupal 7 version of this module can be radically simplified, thanks to the new hooks. See the upgrade documentation for details.

This module will still be necessary in Drupal 7, however, since it tracks the nodes stored in the {menu_links} table.

For Drupal 7, you might also investigate the following modules, which provide similar functionality:

Previous/Next API

An API for browsing next/previous nodes without overloading your database server.

Description

This module allows you to know the previous or next nodes for any given node. This is very useful for providing navigational links to the user without the expensive queries required to dynamically deduce such information on the fly.

The use case is two fold:

Usability/Navigation

For example, on a site with a gallery of images, you want to show a next/previous link with a thumbnail under each image. Your site's visitor click on the link to show new content or browse it.

Scalability

Although the previous and next nodes can be deduced with some SQL work, the queries to do so are very heavy on the database, and can bring a site to its knees. This module solves this problem by storing the previous/next node in a table so lookups are fast. Once the module is installed, it will build this index backwards via cron until all nodes have been indexed. See the "More Info" section below for a detailed post on the positive scalability impacts of implementing this module.

Configuration

The module can be restricted to certain content types to be included in the previous/next indexing. For example, you want the site's visitors to browse through video and image nodes only, but not blogs and regular pages.

Spamicide

The purpose of Spamicide is to prevent spam submission to any form on your Drupal web site. Spamicide adds an input field to each form then hides it with css, when spam bots fill in the field the form is discarded. The field, and matching .css file, are named in such a way as to not let on that it is a spam defeating device, and can be set by admins to almost anything they like(machine readable please). If logging is set, the log will show if and when a particular form has been compromised, and the admin can change the form's field name (and corresponding .css file) to something else.

Strongarm

Strongarm gives site builders a way to override the default variable values that Drupal core and contributed modules ship with.

YUI Grid

YUI Grid

Clean, pure CSS tableless starter theme based upon YUI normalize, fonts, and responsive grids, with ARIA Landmark Roles. YUI Grid 3.x release is fully responsive.

The upcoming YUI Grid 7.x-3.4 will feature elements from PureCSS, which will offer some elegant default styling to build a layout on. YUI Grid itself is extremely bare, and intended as a base theme for projects which will be designed from the ground up.

Pages

Subscribe with RSS Subscribe to RSS - Actively maintained