Developer tools

Contactlink provides a "contact the author" link for nodes and comments. Admins can choose which content types to display the links for.

This Module enables both developers and end-users to introduce asynchronous loading into the normal node listing.

Dript is a scripting engine running around Drupal. Dript can be used by other modules to add scripting or formula capability. The module itself implements a filter that can be applied to nodes and other contents. Dript is simpler and safer than PHP. It is meant to be a glue language similar to formula in spreadsheet with the casual programming concept "once coded it will be forgotten". As a dialect of LISP and a simpler LISP, Dript is for non-programmers who want to alter their contents slightly according to certain behaviors. Dript will give ordinary users or administrators a capability to add function and logic on the fly while working with Drupal without having to go down with PHP or creating a module.

Submit Again can re-route users immediately back to node/add/xxx pages after they have submitted a node. It can be turned on for each content type and is off by default. It includes a theme function to control whether or not a status message is displayed to alert users of the location of their recently submitted posts.

Releasemonitor is a Site Administrator Module that assists with keeping contributed modules up to date and summarizing their upgrade availability. The Release Monitor reads the current version information of enabled contributed modules from the module.info file if they are available, from CVS/Tag and the CVS $Id$ string. Using cron, it gets the current version information to determine if there are minor or major upgrades available. The Monitor displays this information on a single page and creates watchdog events when an upgrade is available. To make downloading easier, it gives links to the Drupal project page, and the CVS repositories (if appropriate).

Given that update_status is in 6.x core, the cvs_deploy has been release, and I am overwhelmed with other work, I am discontinuing all support for releasemonitor. I do believe that releasemonitor has the potential to offer something a little better and different than update status, but I simply don't have the time to do it. Please do not create any issues for this module, they will be ignored and not appreciated.

The monitor currently gets version information from cvs.drupal.org, but future versions whould get this information from the drupal.org project.module. The monitor pulls module information once per day, although this is a configurable option.

Provides placeholder variables (tokens) and an interface for browsing available tokens. As records are displayed, contextual values are replaced, such as [node:title] or [user:name].