Drupal 7 Module Development

Chapter 6
'access arguments' => array('delete artworks'),
'weight' => 1,
'type' => MENU_LOCAL_TASK,
'context' => MENU_CONTEXT_INLINE,
);
}
// ...
This menu item calls drupal_get_form directly, specifically loading the artwork_
delete_confirm form created by the function of the same name:
function artwork_delete_confirm($form, &$form_state, $artwork) {
$form['#artwork'] = $artwork;
// Always provide entity id in the same form key as in the entity
edit form.
$form['aid'] = array('#type' => 'value', '#value' => $artwork->aid);
return confirm_form($form,
t('Are you sure you want to delete %title?', array('%title' =>
$artwork->title)),
'artwork/' . $artwork->aid,
t('This action cannot be undone.'),
t('Delete'),
t('Cancel')
);
}
Rather than build a complete form, we will simply pass data on to a utility function
of the Form API called confirm_form(). confirm_form() takes a number of
parameters: a form array, a question to ask, a path to redirect to if the user changes
his mind, a label for the Yes I mean it button, and a label for the No, I changed my
mind link.
The only form information we need is the artwork to be deleted. Neither will be
displayed but we need to pass them along to the submit callback. The rest of the
parameters are simply text to display to the user.
If the user submits the confirmation form, then we know he really means it. The
submit callback handles deleting the artwork:
function artwork_delete_confirm_submit($form, &$form_state) {
if ($form_state['values']['confirm']) {
$artwork = artwork_load($form_state['values']['aid']);
artwork_delete($form_state['values']['aid']);
[ 179 ]