Administration

The Scheduled Actions module provides support for scheduling and managing Actions to be invoked in the future.

The Crossite plugin allows you to share nodes across a Drupal multi-site configuration such that certain nodes belong to certain sites. This is a form of ultra-cheap aggregation where all the data of the nodes in a Drupal multi-site is shared across all the sites. Practically speaking, when you visit the node page that belongs to a different site than the one you are current on, you will be redirect to the other site.

Notifies delegated roles and custom users about new user registrations.

Node History is a replacement for the revision list built into the node module.

With this module you can configure which columns are displayed in the revision list and how they are formated. A hook is provided for other modules to add columns or format rows and columns.

The columns provided by this module are the same as the built-in ones (vid, author, date, operations, log message).

This module allows you go to the edit page by double clicking on any internal link to an item.

Users with the proper permissions can double-click on:

• node links to go to the node's edit page
• user links to go to the user's edit page
• comment links to go to the comment's edit page

This module also creates hook_dblclick() which allows other modules to provide double-click, shift-double-click, and alt-double-click behaviors. See the module code for documentation and examples.

Provisionator is a utility module for use in managing the deployment (provisioning) of new sites in a shared Drupal hosting environment.

This module provides an extension to the builtin checkboxes element that allows developers add "check all" / "toggle" / "uncheck all" actions to them. This is specially useful for checkboxes that have a lot of elements.

Please note that Drupal 6 already has this feature available, but only for checkboxes rendered in tables, such as those used in Administration -> Content management -> Content. Checkboxes rendered elsewhere do not have this feature.

You may need to install this module when required/recommended by another contributed module, and/or you may wish to use it to enhance your own custom modules.

• For Site Administrators - New option for checkboxes implemented by CCK Widgets

  If you use checkboxes implemented by CCK optionwidgets, node reference, user reference or content taxonomy options, then a new option in the field settings form is available to enable the Checkall feature for those widgets.

• For Developers - Simple Usage

  To attach the checkall behavior to checkboxes elements, all you need to do is add the '#checkall' property to them. You can do so for your own forms, or you can implement hook_alter_form() to add this property to existing forms. Example:

  $form['foobar'] = array(
    '#type' => 'checkboxes',
    '#options' => $options,
    '#default_value' => $default_value,
    '#checkall' => TRUE,  // <--- this is it ;-)
  );
  

This module addresses a specific workflow for publishing nodes where nodes are to be created in published, unmoderated form, but approved by an administrator at a later time. It provides three extra tabs on the admin/node page; approved, disapproved, not yet moderated.

The controls on these three new pages allow you to approve, disapprove, edit or delete nodes.

Wishlist

The module does not yet do these things, which might be useful to some people:

This module addresses a specific workflow need where comments are to be written in a published and unmoderated state, appearing immediately on the website, but should be available for approval or disapproval later. To achieve this, three new sub-menu items are added to the admin/comments screen; "approved", "disapproved" and "not yet moderated". From those three new screens, administrators can approve, disapprove, edit, or delete comments.

This is a sysadmin & developer tool that adds extensive tracing facilities for Drupal hook invocations, database queries and PHP errors.

For an introduction, read the original blog post at:
http://ar.to/2006/12/easier-drupal-debugging-with-trace