Utility

This module lets you drag-and-drop the fields of any CCK content type, Webform, or almost any other form in Drupal into the positions you would like for editing. This makes it super simple to have forms with inline fields, which you can change at any point. Tab indexing is also updated, so no matter how you arrange the fields, the users can still tab through them easily. And, you can now add arbitrary bits of HTML markup-- labels, images, HR's, etc.

Features

• Drag and drop fields into any arrangement you want. Makes Drupal forms look more like pen-and-paper forms.
• Resize textfields and textareas by dragging.
• Make labels, radios, and checkboxes appear inline with the click of a mouse.
• Add HTML markup directly to the form - labels, captions, images, HR's, etc.
• Edit CCK & Webform configurations for each field (required, help text, allowed values, etc) in a popup without having to leave the page.
• Ability to import/export arrangement definitions.
• New in 7.x: Snap to grid when resizing elements (experimental for the moment-- configure on the Settings page)

Date Popup Authored provides a jQuery UI datepicker for the Authored on date field found on node submission forms.

This allows content editors to pick a human-understandable date and not have to type the exact date format of the default Authored on field.

This module allows you to insert tokens into a textarea. It supports both plain text and wysiwyg textareas. The format used for the insert is compatible with Token Filter.

This module contains three modules:

Normally drupal.org inserts version information when a project is packaged. Git repositories do not contain this information. Git Deploy hooks into the Drupal update system and attempts to provide the version of modules and themes checked out of git.

The 2.x version of git_deploy is recommended because it is much more stable but it does require the git binary and the ability for PHP to execute shell commands. The 2.x branch also introduced a new numbering scheme allowing for PHP version checks to work during development.

This is a utility module for developers deals with a specific problem: If a module loads its own Javascript and/or CSS files in hook_form_alter() - and then there is an error if the form is re-submitted because the hook will not be called again (the form is cached) which means that, on page reload, the Javascript and CSS files are not reloaded.

Allows administrator to set up automatic purging of forum posts by date.
e.g. delete Classifieds forum posts older than two months.
If a post has a comment more recent than the delete threshold, it won't be deleted.

Context: Menu Block allows the Menu Block module to be aware of contexts provided
by the Context module by informing menu blocks of active menu context reactions.

This project has recently been taken over and for the time being it will be maintenance fixes only and support but once the code has been fully got to grips with, I intend to actively develop the module further.

This utility Drush add-on just deletes text files (not needed but are) packaged with Drupal; files like INSTALL.txt, UPGRADE.txt, README.txt (in multiple places), etc. This plugin is largely obsolete, or just dated since modern Drupal/web server configurations can deal with protecting these files from being accessed.

Allows users to create block instances of predefined block types registered by other modules.

Features

Difference to core blocks:

• Modules register block "types".
• Administrators can spawn new instances of a block type.
• Block instances are entities.
• Unless a block type opts out, Block API takes over the storage of configuration settings per block instance.

Major ideas and parts for the block instance handling have been based and borrowed from JohnAlbin's excellent Menu block module.

An example API implementation is available in a hidden testing module, which provides the equivalent of custom blocks in core; i.e., a simple title and HTML body.

Block API itself provides no block types on its own.

This is a very simple module that exposes a 'redirect' task to the page manager module in the ctools suite. This allows you to define paths that can then redirect to others, all without writing any code. You can use this to do things like:

• Redirect user profile nodes to the /user/X page that owns the profile
• Redirect Images in a gallery to their node referenced gallery.

Page Manager Redirect (PMR) is now fully compatible with Drupal 7!

Differences from similar modules

There are a number of other modules that attempt to perform some kind of redirection based on paths. Page manager redirect is different because it can leverage the ctools context system to gather all sorts of useful information from the original URL to construct the redirection URL with. Genius!