Administration tools

Makes it easier for editors to place their content exactly where they want it inside their menus.

This module adds a menu browser to the content forms. Users don't choose "parent" and "weight" for the menu item they are adding. Instead they choose a menu, and the menu gets loaded using ajax. The users then places the menu item inside the menu by clicking on the item they want to place the menu below. New menu items may also be placed as children of existing menu items.

The Menu Expanded module is a simple module designed to revert the changes made in

Drupal 7 has a new and efficient way of loading module and theme settings from the database. The new loader requires all settings to be stored in the current (serialized) format.

An unfortunate side effect is that any left-over settings from modules that did not clean up when they were uninstalled, and are not stored in the correct format, cause PHP notices on your site.

This may happen if you've for instance upgraded a site from Drupal 5, through Drupal 6 to Drupal 7.

This module lists all entries in the {variable} table that cause unwanted PHP notices on production sites, such as:

Notice: unserialize() [function.unserialize]: Error at offset 74 of 75 bytes in variable_initialize() (line 749 of /srv/www/<sitename>/includes/bootstrap.inc).

By knowing the offending variable name, you can remove it from the database, making the notice go away. Of course, you should probably notify the module or theme author that their module or theme does not properly clean up after itself.

If you find a variable that causes a problem, please note it in a comment on #1284364: Use variable_initialize() against broken values - Notice: unserialize() [function.unserialize]: .

Related Modules

• Variable Cleanup — Checks for unused variables in your variable table by scanning your entire filesystem for unused variables.
  

This module provides more features for developers and themers when they debugging drupal.

It's often useful to provide two versions of a given string: one that's intended for human viewing and another that's intended for use in database queries, URLs, and so on.

In Drupal, this is generally known as a 'Name' and 'Machine name' pair. Drupal 7 even provides a prefab FormAPI element to simplify the process of entering these matched pairs.

Safeword exposes a custom FieldAPI field type that stores two strings using the name/machine name approach. It can be useful when generating PathAuto aliases, exposing Views arguments, and so on.

One common use is to not give users permission to 'Create and edit URL aliases' and instead give them access to a Safeword field which uses the node title as it's source. So that users can only edit a limited part of the path, keeping safe the other parts that your site features may rely on.

This is an add-on module for the Aegir hosting system:
http://aegirproject.org

Aegir 2

For the same features for Aegir 2 and above have a look at Hosting site backup manager.

Introduction

This module allows you to specify how long Aegir should retain backups for. You can specify, for example, that after a month, only one backup a week should be kept. You can specify as many of these rules as you want, so you could keep hourly backups for a day, daily backups for two weeks and monthly backups thereafter.

Currently it applies to all sites hosted by Aegir, and there is no way to exclude specific sites.
Installation

1. Install as any other Drupal module into your hostmaster site.
2. Enable the feature in the 'experimental' section of 'admin/hosting' page.

Configuration

1. Settings are available at 'admin/hosting/backup_gc' and allow you to choose the numbers of backups to keep after specified periods of time.

Friendly warning

This module removes backups, but may not work perfectly, and might remove backups that you don't want removed. Although, if you are sensible about the settings used you won't lose any backups that you might want to keep.

Related modules