Utility

How do Drupal's nodes relate to each other? Assuming nodes with type of 'person', 'group' and 'product', how can we express...
...that person Fred is A_MEMBER_OF group Salesforce since 1989 and that he became LEADER_OF group Salesforce in 1995.
...that person Fred is A_COLLEAGUE_OF person John and A_SUPERVISOR_OF person Bill.
There are no limits to how the model of an organization might evolve and what might become relevant: For example, we also might want to track...
...that person Bill HAS_BOUGHT product DrupalBook on Oct. 17, 2005 for $19.95.

Inline Registration allows anonymous users to register via the node/add page, thus removing a step/barrier from the user actually publishing content. If you're going to use this module, or allow anonymous users to post content to your site at all for that matter, you should really use CAPTCHA to help keep the spam-bots from trashing your site.

Upload Log is a module which allows direct uploads from programs to a Drupal site (with authentication, through the HTTP Authentication Module). The sending of notification e-mails is possible, as is data validation.

A demonstration is available in the WaterSums software.

Any programming language that supports HTTP uploads with HTTP authentication can be used to send log files.

The aim of the JavaScript Aggregator module is to improve performance of your site with less server requests and bandwidth per page. In Drupal 5, all the JavaScript files will be aggregated into one file and optionally minified. JavaScript aggregation was brought into core with Drupal 6, so the Drupal 6 version of this module goes one step further to minify that file.

It basically does the following:

• Takes the $scripts variable and removes .js files using a regular expression
• Generates a unique filename for any set of .js files
• Creates and caches one file containing all .js files in files/js
• Optionally minifies the JavaScript using JSMin
• Returns a modified $scripts variable with link to cached file

I have not found an official "heres the way to email everyone in a certain role(s)" action, so I've cleaned some code and contributed it.

This module provides an action which is configurable to email everyone in the specified roles, it is much like the built in "send email" action however it allows you select the recipients as a list of roles.

The action is usually implemented as a trigger.

Basic usage;

- Enable 'triggers' module admin/build/modules

This module is intended for administrators who have to jump around to specific pages while managing Drupal sites. It's a hotkey-activated launcher utility inspired by Quicksilver, Gnome Do and other desktop launchers. A configurable hotkey (Ctrl-M by default, or Crtl-T in older versions) brings up the dialog. Type in any part of the title or path of the page and an autocompleted list of possibilities will pop up. Unlike many other dynamic search modules, Teleport searches titles and paths of system pages as well as node titles. See this short screencast for a demonstration.

If you don't want to wait for the autocomplete to finish, you can just type a query and submit the form. Teleport will guess what you mean and send you right there, or display a list of options if it can't figure it out.

Development generously sponsored by Trellon.

This module has been abandoned in favor of multiblock. Use that one if you want multiple instances of a block.

Help toggle adds a 'Hide help'/'Show help' link on pages that contain help text or field descriptions for hiding and showing them.

Requirements

This module uses jquery.cookie.js to set cookies in javascript. You can download the latest version from https://raw.github.com/carhartl/jquery-cookie/master/jquery.cookie.js. Place the file in sites/all/libraries/jquery.cookie. See the README.txt for full installing instructions.

Gives the recent log entries page auto update functionality. Great for a dev watching the logs of a live site.

The feature can be turned off without disabling the module and an update interval can be set.

The D7 version has a soft-dependency on the Beautytips module. If you install Beautytips, you will get neat mouseovers with log info on the entries in the log.

Plans for the future include:

*** See #315100: Allow to add JS/CSS libraries (sets of files, settings, and dependent libraries) for the patch to put jQ in core! ***

The jQ module allows other modules to register jQuery plugins in a central repository, and allows administrators of a site to enable or disable specific plugins globally.

The concept behind this module is to create a basic hook structure for jQuery wrapper modules, allowing other modules using these plugins to invoke them in a consistent fashion.

(Drupal 6 version only): You can also simply add new jQuery plugin files in your /plugins or /sites/example.com/plugins directory, and they'll be added to the registry. Then, for example, if you upload jquery.example.js, you could just jq_add('jquery.example'); and you're off. Additionally, if you have a .js and .css file with the same base name there, they'll both be added with the same call. Caveat: if you have two plugins with the same base name, there are no guarantees which will be added to the registry. Better off defining a hook_jq function in that case (see below for information on that).

Kudos to jjeff for his work on the jQuery Plugin Handler (JQP) module that inspired this latest functionality.