Unsupported

This module allows to render breadcrumbs according to a hierarchy of nodes defined via node reference fields.

View and post issues to Github without the need to actually have a Github account.

This can be useful in companies in which users may find issues in software, but since they are users and not coders, they may not have a Github account.
However we still like to hear from them.

Persistent Identifiers provides methods for creating storing and retrieving persistent identifiers of different types, including URIs, UUIDs and machine names.

This project is on hiatus indefinitely. If you are interested in development of this module, please contact the maintainer.

This provides some reporting functionality intended to be used with Commerce POS.

Drupal 6 outputs XHTML 1.0 strict by default. As of W3C standards, all elements ("tags") as well as their attributes have to be defined lowercase, e.g. <br /> instead of <BR />.

Unfortunately, almost any existing WYSIWYG does not pay respect to this and, instead, sticks to the common Javascript/jQuery habit to regard and output DOM element names uppercase. Thus, almost no page content created in one of these editors will ever display standard compliant code.

Using an antivirus tool on your Drupal site, but this module doesn't yet support it? Please post a feature request so that we can get it included!

Overview

An evolution of the current ClamAV project, this module looks to be a more generic solution to allow integration with a number of different anti-virus tools and providers.

The Storm Knowledge Base module provides a simple way of managing knowledge as part of the Storm set of modules.

Since January 2012, Storm Knowledge Base has been maintained as a separate project.

You only need to download this project if you are using Storm 6.x-2.x onwards.

UPDATE

Turns out this module already exists. It's called Environment Indicator by mrfelton. Thanks to stella for pointing that out in #1398060: environment indicator module.

I'm therefore retiring this project.

This is a temporary demo of what Larry thinks a module might look like in a WSCCI world, kinda sorta, as of early January 2012.

Disclaimer: Not one single line of code in this module should be taken as a promise, guarantee, or roadmap. This is "What Larry kinda sorta thinks a module will look like in a WSCCI world, brain dumping, without thinking all parts through yet". This code likely will not even run if you tried. Just about the only thing I can guarantee about it is that NetBeans tells me there are no obvious syntax errors. Otherwise, caveat emptor.

[NOTE: This module has been deprecated as of June 2013 in favor of Cache Expiration. If you're currently using Boost Expire, please follow these directions to switch from Boost Expire to Cache Expiration on your site!]

A cache expiration module to go with Boost for Drupal 7.

Currently, Boost for Drupal 7 doesn't do any active cache expiration (see #1069438: How to Flush Boost Cache in Drupal 7.x), and this means that when you update a node, post a comment, etc., Boost will continue serving stale content from its static HTML cache until the file is finally cleaned up on a cron run.

For many sites, especially smaller sites where content is updated infrequently and cron may be run hourly or even less frequently, this means stale content will be served for quite some time, unless someone visits the Performance page and clears all the site's caches manually.

This module alleviates that problem by simply flushing Boost's static HTML cache every time a node or comment is posted or updated. You can set the module to respect your site's Minimum cache lifetime so it doesn't flush the cache until the minimum lifetime has passed.

This module may become deprecated in favor of a more universal solution (like Boost integration with the Cache Expiration module).