Administration tools

This module allows users to submit incident reports from a Drupal site.

Drush scripts for creating Drupal sites from a shell. Tested with Debian and Ubuntu.

A state machine for paranoia, with the halting state typically entailing the implementation of a scorched earth policy response (i.e., erasing the Drupal database). Think DEFCON for Drupal.

This module is meant primarily for "paranoid" Drupal use cases involving information warfare. Typical users might be political dissidents in repressive regimes, BitTorrent bootleggers, various kinds of activists, and so on and so forth.

Basically, if you have adversaries trying to hunt & shut your site down or limit your ability to disseminate information, you'll probably want to install Lockdown to help maintain tight information discipline as well as to guard the perimeter and perhaps give you some advance warning when it's getting to be time to move shop.

This module is only provide API for other modules.

Features

This module allows for other modules:

• To specify structure and default values of all module settings in one place by using "hook_get_settings()".
• Use variable naming standards: <module_name> "_" <setting_name>.
• Use defined default values everywhere (with option to override default value).
  So, you don't need to specify same default value for every "variable_get()" call.
  Also if you will decide to change default value of your setting, all you need is to change it in the "hook_get_settings()" implementation, not on every "variable_get()" call.
  Example:
  Instead of variable_get('my_module_var1', 456) in several places of a code, you can just use settings_get_for('my_module', 'var1') or even settings_get('var1') if you get a value of your own module from itself.
  To override default value use the same approach as for "variable_get": settings_get_for('my_module', 'var1', 987) or settings_get('var1', 987)
  ^{(This will override default value with "987".)}
• Automatic check for existence of setting at the moment of "set" or "get" and in case if setting it's not defined raise an error. This will keep your code consistent with your settings.

This module allows user to move content (nodes) to trashbin. It inserts "Move to trash" button on node edit page, for users who have permission to move this node to trash.
What is trashbin then ? It's for you to decide. This module was made as simple as possible, providing minimal interface on it's own, but serving as bridge module for other modules at the same time. It provides hook which is invoked when user presses "Move to trash" and confirms the action.

This module became obsolete, because Flag module now has access control built-in. You can do same things with the Flag module

Taxonomy Export is a light-weight module for managing exports and imports of vocabularies and terms. Currently the following features are supported:

• Exporting vocabulary definitions
• Exporting vocabulary definitions with all terms
• Creating exports as a text string (ie: like Views and CCK's content_copy)
• Creating exports as a file
• Importing vocabulary / term definitions in install profiles, using Install Profile API
• Updating existing vocabularies and terms, with the following caveats:
  1. Updated items must have the same VIDs / TIDs. Just because two things are named the same doesn't make them the same. It is safest to attempt updates only on the same site the export was originally taken from.
  2. When updating you must explicitly state (with the dropdown selector) which vocabulary you want to update.
  3. Currently, updating vocabularies using the IPAPI function install_taxonomy_export_import_from_file() is not supported.
  4. Because of limitations in Drupal's taxonomy.module implementation certain things will, likley, never be possible. For example, detecting malformed imports that could cause collisions.