Developer tools

Introduction:
-------------
There is currently no easy way to download and share the complete manifests of a Drupal installation:
* Which version is installed?

#D7CX: I pledge that services will have a full Drupal 7 release on the day that Drupal 7 is re

This module uses custom jquery + css + html to replace a standard drupal single dropdown with css-driven dropdown that has much more flexibility with styling than the default browser select element

This module provides an API to shorten URLs via many services like bit.ly and TinyURL (over 15 services are available by default), as well as a block and a page that provide an interface for easily shortening URLs, and a block that displays a shortened URL for the current page for easy copying.

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:

• http://drupal.org/project/entity_index

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.