Developer tools

BuzzMonitor is a semantic engine that allows aggregation (using FeedAPI), categorization and analysis of news content, from all over the Web, via integration with some of the most advanced modern A

The Menu Node Views module provides Views integration for nodes assigned to the menu system. This module is in alpha development.

database Change Management (dbCM) lets user to compare the changes made in local database over a period of time.

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 is not actually a module, but an include file to use in hook_update_N() calls. The file contains helper functions for common update tasks, such as renaming variables, installing and reverting features, granting and revoking permissions, deleting and altering CCK fields, changing content type information like Title label, etc.

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