Actively maintained

SignatureField allows you to collect HTML5 canvas based signatures in webform, cck and in your custom modules via fapi. It then displays the collected signature as a transparent png. SignatureField works with both mouse and touch devices.

It achieves this using the Signature Pad jQuery plugin from:
http://thomasjbradley.ca/lab/signature-pad

SignatureField Drupal 7 development has been sponsored by:

This module provides integration between the txtlocal SMS service and the SMS framework module.

This is a new module I'm currently working on to support "hidden" and "value" form widgets for fields in Drupal 7. The module is based on some code chx threw together after a discussion on IRC.

The code still needs some tests and polish, but it is usable today. It's your data, though, so be careful.

New Relic RPM is an excellent tool for improving and monitoring your Drupal installation. Visit http://newrelic.com for information and the ability to sign up for a free trial of their Pro service. Visit https://newrelic.com/docs/php/new-relic-for-php for instructions on how to install the PHP extension and the reporting daemon.

Nagios Looking Glass (NLG) is a utility for viewing filtered Nagios data.

NLG is not a tool for sending Drupal data to a Nagios server. For this you should use the Nagios Monitoring module.

On the top of this project page is a screenshot of the module in action, with some custom theming added to it.

7.x. Version

7.x Version by Daniel Baker

Stage File Proxy is a general solution for getting production files on a development server on demand. It saves you time and disk space by sending requests to your development environment's files directory to the production environment and making a copy of the production file in your development site. You should not need to enable this module in production.

About

Drupal Guestbook Smileys (DGBS) provides Smileys module integration
for the Drupal Guestbook (DGB) module.

The jEditable module provides integration between Drupal's CCK module and the excellent jQuery plugin, jEditable. It is implemented as a CCK formatter, which makes inline editing possible through regular node displays, Panels, Views, or anywhere else you can place a CCK field.

Currently supported features are "click to edit" functions for text fields, number fields, date fields, node reference fields and workflow transitions.

So what is this good for? it provides a very quick and easy way to update the things they need to change without having to edit specific fields without having to switch to the full-blown node editor.

It is with Views integration that jEditable really comes into its own. It allows users to edit many nodes at the same time, e.g. if the same field must be updated for many nodes.

Major overhaul

This module is undergoing a major rework to make the it more suitable for mainstream use. The latest 6.x-1.5 release provides complete input validation of all supported fields as well as formatting. The module also provides user confirmation that the new field value was actually stored in the database.

New in this release is Views integration which moves away from using formatters, thus restoring them to their original purpose.

Further development will be made on the a new 6.x-2.x branch which will break 6.x-1.x versions of the module. Specifically, the jEditable formatters will be removed along with the 'Create Node Revisions' admin setting.

By default, the Drupal menu system only allows you to add menu items that are links. With this module, you can add menu items that are simply containers, and not links.

These containers are just standard menu items, so they work with any module or theme that works with core's menu module. But these containers have these special traits:

1. Containers have no URL path associated with them. So they are not links, just regular text.
2. Containers are menu items that are always expanded. Since you can’t go to the container’s “page”, the only way to see its children links are for the container to be always expanded.
3. The HTML wrapper around the container’s title is controlled with theme_menu_item_container(). See the README.txt for more info.

Wysiwyg Linebreaks allows users of wysiwyg editors to save and open markup from their website with linebreaks instead of <p> and <br /> tags.

You can choose between two different methods:

• Force linebreaks: Your content will always preserve whitespace/linebreaks around blocks of text, rather than paragraph and break tags.
• Convert linebreaks: Your legacy content will appear correctly in your WYSIWYG editor, then the content will be saved with the markup added by the editor).

The 'force' option is useful for sites where you would like to edit content both with and without wysiwyg editors (so you don't have to manually enter paragraph and linebreak tags everywhere).

Basically, you can edit content that was originally created without a wysiwyg editor (for instance, simply using Drupal's Filtered HTML format, a user may hit enter twice to create a new paragraph—no <p> tag wraps the block of text in this case), without having to deal with the headache of reformatting everything inside the wysiwyg editor.