The Drupal shell. See


The PatchInfo module allows you to add information about patches to a modules .info file. It will show the information prominently in the update report and on the update manager form.

External Logger

External Logger - WIP

TamTam External Logger module for Drupal is a module that utilizes hook_watchdog() to catch all log events on a Drupal based site. And send the events to a compatible backend. The module is designed to center log messages of multiple environments and sites in a single location. All environments can be grouped to form a practical overview. Saving the developer the time of looking up multiple logs and/or multiple machines.

Entity Process Callback

Many times you want to execute an operation over a list of entities. Sometimes you will want to retroactively apply a default value to a certain field, other times you will want to export the articles tagged as Drupal to a CSV file, etc.

This drush command simplifies that process for you. You only need to write the callback function that does your operation, given an entity. All valid callbacks will receive the entity type as the first argument and the loaded entity as the second parameter.


Hosting Variables

This Aegir module allows you to set arbitrary custom Drupal variables for each site, such as site name and slogan.

These variables will be put in settings.php, and so can't be overriden (or changed) through the site interface.

This module is only compatible with Aegir3.


Extra SiteInfo


Extra Site Information module provides Drush commands and UI level view to see the count of Nodes, Content types, Users, Roles existing in the site.
This module also provides the information about Currently loggedin users in your site.


"nodetypecount" command will return the number of Content Types present in the site, you can use command in following ways.
drush nodetypecount --help
drush nodetypecount

Updates Development

When you are developing new module or some migration stuff, you will probably need to work with update hooks. Drupal core functionality allows to execute each update hook only once (and it should be like that). But some times you need to fix something and try to execute update hook again, in that case you will probably go to DB and update schema version or increase update hook number in the module. In first case it's not a problem, but takes time. In second case it potentialy may bring problems with update numbers, since it's not hard to forget to update hook number back before commit.


Subscribe with RSS Subscribe to RSS - Drush