Drupal 7 Module Development

Chapter 5
'#description' => t('Indicates whether the admin user (as set in
site configuration) should be BCC\'d on all warning e-mails.'),
);
}
return system_settings_form($form);
The first thing you'll notice is that we no longer have a submit button element. That
is because system_settings_form() adds one in for us automatically. It gets the
label 'Save settings'.
Additionally, system_settings_form() uses its own custom submit handler
system_settings_form_submit(), which automatically saves all form elements
into persistent variables of the same name. You don't have to write a submit
function at all, Drupal takes care of everything behind the scenes.
It might seem silly to use an API function for something as simple as adding a
submit button and automating the handling of persistent variables. However, the
less code you have to write the less bugs you introduce. With just around 30 lines of
code, we now have a fully functional form with extensive validation, customizable
default settings, and the ability for users to change the default settings as they wish.
Having set up our module's configuration form, we now need to add a function that
enables administrators to actually send this e-mail to users.
A shortcut for confirmation forms
Earlier in the chapter, we added a 'Warn' tab to user profile pages. System
administrators should be able to click this tab to send the warning e-mail to users.
However, it would be nice if we could add a confirmation step here, to prevent
e-mails from being sent inadvertently.
This is another situation where Drupal offers a convenient shortcut function.
Let's revisit the callback function we looked at earlier while discussing 'value'
form elements.
/**
* Form builder; display the e-mail confirmation form.
*/
function user_warn_confirm_form($form, &$form_state, $uid)
{
$form['account'] = array(
'#type' => 'value',
'#value' => user_load($uid),
);
[ 139 ]