Drupal 7 Module Development

Chapter 6
array($artwork->aid => $artwork),
$view_mode);
entity_prepare_view('artwork', array($artwork->aid => $artwork));
$artwork->content += field_attach_view('artwork', $artwork,
$view_mode);
}
return $artwork->content;
The title callback needs no explanation. The artwork_page_view() function
again doesn't do much beyond shepherd data off to the Field API. In particular, note
that it does take a $view_mode parameter, which should be one of the view modes
we defined back in the artwork_entity_info(). Even if we don't want to leverage
it ourselves the Field system will require it.
If we're in "teaser" mode, we want to inject the title of the artwork into the viewable
result. If not, we have no data to display other than the attached fields as the title is
already being displayed as the page title. The field code is a fairly boilerplate three
lines of code that produce a renderable array, which we simply return.
That wasn't so hard, was it?
Editing an artwork
Now that we have artworks we can see, we want to be able to go back and edit them.
Fortunately most of the work we already did as part of the creation process. In fact,
we're going to reuse the same form and same save() method of the controller. All
we really need to add is the page callback to use it.
function artwork_menu() {
$items['artwork/%artwork/edit'] = array(
'title' => 'Edit',
'page callback' => 'artwork_page_edit',
'page arguments' => array(1),
'access arguments' => array('update artworks'),
'weight' => 0,
'type' => MENU_LOCAL_TASK,
'context' => MENU_CONTEXT_PAGE | MENU_CONTEXT_INLINE,
);
// ...
}
function artwork_page_edit($artwork) {
$types = artwork_types();
[ 177 ]