Drupal 7 Module Development

Building an Admin Interface
$items['user/%/warn'] = array(
'title' => 'Warn',
'description' =>
'Send e-mail to a user about improper site behavior.',
'page callback' => 'drupal_get_form',
'page arguments' => array('user_warn_confirm_form', 1),
'access arguments' => array('administer users'),
'type' => MENU_LOCAL_TASK,
);
}
return $items;
Like many Drupal hook implementations, hook_menu() returns a structured
associative array with information about the menu items being defined. The first
item in our example defines the module configuration page, and the second one
defines the user tab where administrators can go to send the actual e-mail. Let's
look at the first item in more detail.
Menu items are keyed off their path. This is an internal Drupal path with no leading
or trailing slashes. This path not only defines the location of a page, but also its place
in the menu hierarchy, with each part of the URL being a child of the last. In this
example, people is a child of config which is itself a child of admin.
If a requested path does not exist, Drupal will work its way up the hierarchy
until it encounters a page that does exist. You can see this in action by requesting
admin/config/people/xyzzy which displays the page at admin/config/people.
If you are creating a menu item for site administration it must begin with admin. This
places it into Drupal's administrative interface and applies the admin theme defined
by the site settings.
Module-specific settings should always be present under admin/config.
Drupal 7 offers several categories which module developers should use to
better organize their settings according to Drupal functional groups like
People and Permissions or Content Authoring.
The value associated with this key is itself an associative array with several keys that
define what action should be taken when this URL is requested. We can now look at
those in detail. The first item defines your page title:
'title' => 'User Warn',
[ 122 ]