Utility

Why Do I Need It?

Unfortunately Drupal does not include the powers of immortality or invincibility. You may someday get hit by a truck, or even just decide that you no longer want to maintain the site. So someone else may have to take over.

Where do they start? I know you documented the site really well, but the next person doesn't want to read those 14 binders of documentation you left behind. They can always go through all the administration screens and look for the information, but that can take a lot of time and even those pages don't tell you everything. Some things you're only going to get by looking directly into the database.

This is what the Site Documentation module is designed to do. In addition, it will detect some problems that may exist in your installation, and optionally correct some of them.

Enables custom requiring and hiding of designated modules at admin/modules. Good for Drupal distros and hosts.

A good example would be to prevent the disabling of the paranoia module, which prevents PHP from being run.

systemmask development has been sponsored by CivicSpaceLabs.org. After May 10, 2007 the module has been maintained by Robin Monks.

The advanced caching module is mostly a set of patches and a supporting module to bring caching to Drupal core in places where it is needed yet currently unavailable. These include caching nodes, comments, taxonomy (terms, trees, vocabularies and terms-per-node), path aliases, and search results.

The HTML2Book module allows you to create multi-page books by splitting the body text of a book page node into multiple nodes upon save. The split points are based upon HTML heading tags.

This makes it possible to create a book in a word processing program, export the result to HTML, and then use this HTML to create a multipage Drupal book.

This module will not be supported any more since this functionality was already implemented in ecommerce core.

The module should be used within ecommerce package and depends on product.module.
It allows to assign a certain product type to any content type declared in the system (CCK types as well). After that all nodes of this type will be created as products without a need to add them to a store manually.

Provides devnagari (India) transliteration ability to the edit elements of the nodes. using this module any drupal installation can start providing Hindi or Marathi typing facilities on the site.

The block configuration provides facilities to change the preference on which node the transliterator should work.

This Drupal module offers a trouble ticketing system similar to the ancient PHPHelpDesk. It authenticates users from Drupal and classify them to user groups and department units. It provides the following features:

Helped sites that were deployed directly from a CVS workspace, as opposed to sites built via packages downloaded from drupal.org. This module is obsolete now that drupal.org uses Git not CVS. Instead, you should use Git deploy.

This module provides a powerful interface for managing taxonomies. A vocabulary gets displayed in a dynamic tree view, where parent terms can be expanded to list their nested child terms or can be collapsed.

The Taxonomy Manager has following operations and key features:

Oct 20th 2010 - The name of this module, could cause confusion to those using drupal core functions. Additionally there is currently a function name conflict with the ftp code used in the backup_migrate module. This is discussed here: #803964: function name conflicts with drupal_ftp