No further development

This module has exactly a few use cases:
a) The paranoid, tinfoil hat people who don't want Drupal.org to have any information about the modules installed on their sites, even at the expense of their sites being secure.
b) Large organizations with their own Drupal distribution who want to handle the flow of update notifications.
c) Organizations who use a third party administration service which manages updates for them
d) Distributions whom need to control how updates are created.

If you do not fall under these use cases, you probably should not use this module. It will prevent core's Update status module from being enabled, by design. Please see http://drupal.org/node/282919#comment-1074620 for more details.

Drupal requires cookies for user login, but by default no error message is given when a user's browser is set not to accept cookies. The result is a broken site--after attempting to log in, the user is returned to an empty login form with no indication of why login failed.

Overview

DBFM is a file manager based on a hierarchical directory structure and uses AJAX to allow administrators to arrange files in the database in the same way they do with file managers on their personal systems.

DBFM stores its files in a database as opposed to the filesystem. This enables advanced manipulation of the uploaded information. Keywords, notes and other meta-data can be added to uploaded documents, document revision management is now possible. Future revisions of DBFM will include extensive searching of this meta-data.

Abandoned Module: As of October 4th, 2010 this module has been marked as abandoned. If you would like to take over as maintainer of this module, please file an issue in Webmaster Issue Queue.

********************************************************

Spam_Tokens is an add-on to the Spam module. It allows the Spam administrator to control the tokens that are used by the Spam filters to determine whether or not content is spam.

New maintainer wanted. I no longer use Spam (I went to Mollom). Contact me and I will turn it over to you.

Application Module that imports and manages Bills from the U.S. Library of Congress website as CCK nodes. It imports Representatives, Committees, Bills, and Bill Actions. It creates these CCK types when the module is installed, and imports this data on cron runs. It manages the automatic updating of this data as it changes.

It also implements an input filter called the "H.R." filter that looks for references to bills in the input text and converts these to links to the bill nodes. It recognizes several regular expressions, such as HR1234, H.R.1234, and even H.RES.1234 for Resolutions. The input filter must be enabled for the desired input format, presumably "Filtered HTML".

The administrator can control which user is the owner of the Bill nodes, what type of bills to download (Bills, Resolutions, Joint Resolutions, etc), and how much time to spend during each cron run. The module was built with Organic Groups in mind.

The data is retrieved from Thomas via two methods. The primary method is screen-scraping. The secondary method is by reading a document archive of XML files. The reason XML is the secondary method is that not all information is available via XML. However, this second method is important in that it does provide some additional information and it is the main indicator that something in the BIll has changed, and that the screen-scraping should be re-initiated.

This module depends on CCK and date. You must download these projects and put them in your modules directory.

The Visualize Backtrace module enables you to visualize the sequential order of Drupal function calls for a given page load in both a hierarchical tree flowchart and table format. This is a developer's tool that parses XDebug trace files into *.dot GraphViz graphs order to help demystify the Drupal API & identify bottleneck Drupal functions. It can also visualize a variety of specific backtrace and forwardtraces detailed below.

This introductory screencast demonstrates the visualize backtrace module (be sure to expand to full screen mode), and the audio from this Drupal Camp presentation explains it in more detail.

The salt module allows for Drupal passwords to be 'salted' - an internal string is appended to the password prior to storage - making them less prone to dictionary attacks, rainbow tables and the like.

This module currently stores the salted password in the database. Consequently, disabling this module or changing the salt at any time will require users with salted passwords to recover their passwords.

Nocase is a simple module that allows for case insensitive Drupal passwords.

N.B. This module currently stores (and assumes that all stored) passwords in lower case in the database. In other words, it modifies user input (which is not really a good thing) and might require existing users not using all lower-case passwords to reset them. Furthermore, once this module has been installed, uninstalling it is not a recommended course of action as users using mixed-case passwords will not be able to log in unless they type the same password in lower-case.

Patches are welcome :)

The netFORUM Dynamic Facade Nodes module relies on the netFORUM xWeb Interface module and allows Objects from a netFORUM database to become Nodes on a Drupal website. For simplicity it uses the same syntax as Correspondence Templates in the e-Marketing module of iWeb, including conditional statements.

Place is a collection of modules for storing and displaying geographic location data and in Drupal.