Developer tools

Summary

Follow-up allows you to schedule the creation of nodes, triggered by the creation of a node. That is, it allows you to configure a trigger node type with information on the target nodes and the follow-up schedule, and the module will create a schedule for when the target nodes should be created.

As an example, you may have a questionnaire on which you want to collect additional responses from the same users every month for the next three months. The follow-up module will show a table when each next node is due. The follow-up nodes will, optionally, have a node reference back to the node that triggered the schedule.

Requirements

This module does not depend on any other modules, however, it can use the Date and Node Reference modules to provide more functionality. It also integrates with Node Reference URL Widget.

Exporting capabilities are provided by installing the Chaos tools suite module.

Configuration

Once installed, go to ?q=admin/build/followup and click on Add. You will be presented with all the options for configure a follow-up schedule. Once you Save it, it will show up in the table.

Drupal allows you to set your site into maintenance mode in order to deploy code and database upgrades safely.

This module allows developers tracked by the CVS integration module to be associated with an e-mail address, to assist with the migration of CVS repositories to Git repositories. CVS Users will be associated with an anonymous "no-reply" by default. Additionally they will be able to select an e-mail from a list of addresses Drupal associates with the user.

This module has been renamed / moved to http://drupal.org/project/ux_elements

Shepherd is a web based administration tool for web sites using the OpenShift Container Platform.

This module is for fairly advanced Drupal users. It helps manage database settings as they are shared between multiple developers, and also between dev, staging and live versions of a website.

Read the (verbose) introduction.

Be sure to read the README.txt before you enable and use the module! Once enabled:

a) There's a special copy of Drupal where the settings can be changed. It's called the "base".
b) Each table might contain settings and data. It uses database settings to reserve a range of IDs.

The site_update.module does some of the work for you. You have to remember to make settings changes on the special "base" copy of you site. And use a special script to "dump" those settings to a file. The file can then be treated like source code. So it can be checked into a version control system and shared among developers that way.

It is a little tricky to start using site_update on a site that already has a large database. It works best when you use it from the very beginning of every project. I highly recommend you give it a try on your next Drupal site.

Known problems and limitations include:

* The 2.x branch is close to being database agnostic. Primarily tested on mysql, but the goal is to work with any database.