Drupal 7 Module Development

Working with Content
'access arguments' => array('administer artworks'),
);
$items['admin/structure/artworks/manage/%artwork_type/view'] =
array(
'title' => 'View',
'type' => MENU_DEFAULT_LOCAL_TASK,
);
}
return $items;
Once again, while Drupal's big arrays look like a lot of code it is all fairly
straightforward. The first item sets up our artwork type landing page at admin/
structure/artworks (which deliberately parallels the admin/structure/content
path for managing nodes). The second sets up a callback for viewing and editing
each artwork type (bundle), although we won't do anything with it except show
some static information. The third menu item creates a menu tab (or in Drupal
parlance, "local task") called View, that is the default and will pass-through to the
parent artwork-type-manage page.
The tab definition is important. Recall from the last section that our
artwork_entity_info() function told the Field UI system that it should add its
own administrative pages at admin/structure/artworks/manage/%artwork_type.
When the Field UI module is enabled, therefore, it will add additional pages as
tabs next to our View tab. If we don't declare our page as a tab, it will get lost when
someone views the Field UI pages.
There are a few new functions we need here to support these pages, all of them
very short.
function artwork_overview_types() {
foreach (artwork_types() as $type => $info) {
$type_url_str = str_replace('_', '-', $type);
$label = t('View @type', array('@type' => $info->name));
$items[] = l($label, 'admin/structure/artworks/manage/' .
$type_url_str);
}
return theme('item_list', array('items' => $items));
}
[ 164 ]