Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
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 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
Install as any other Drupal module into your hostmaster site.
Enable the feature in the 'experimental' section of 'admin/hosting' page.
Configuration
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.
A UI tweak to hide certain features or the form interface from normal use, but still have them available on the page for validation and quick access.
This slims down the UI to make things seem simpler, without overloading the maintenance tasks with layers of permissions, or removing any control from the user.
USAGE
When enabled, any configured form can have elements hidden (by css) for normal use, and a small client-side button [Advanced] can be pressed to reveal the rest of the form as needed.