Drupal 7 Module Development

Working with Content
There are a couple of moving parts here. First is the create method of the controller.
The entity_get_controller() function creates a new instance of the controller
class for artwork entities, which is the ArtworkController class we defined earlier.
The create method is not part of the normal controller interface but is a really nice
addition. It's quite simple:
public function create($type = '') {
return (object) array(
'aid' => '',
'type' => $type,
'title' => '',
);
}
It's easier to define large data structures in PHP as arrays, so we'll do that and
cast it back to an object to return it. We can now create a new artwork object
from anywhere.
Next is the PASS_THROUGH constant we're passing as the second parameter to
drupal_set_title(). Normally drupal_set_title will strip out HTML from the
title to avoid security issues. Passing PASS_THROUGH as the second parameter tells the
function to allow HTML in the string we're giving it because we've already checked
to make sure it's safe.
Use the PASS_THROUGH flag with drupal_set_title() to allow
HTML in the page title. Remember that means it's up to us to sanity
check and filter the title to avoid cross-site-scripting attacks.
Finally there's the form. We're giving the form a dynamic name so that form_alter
implementations may uniquely target a specific artwork type. How then do we
match that form name with the form builder function that defines it? Drupal
provides another optional hook for us called hook_forms() that lets us
dynamically define forms and how they should behave.
function artwork_forms() {
$forms = array();
if ($types = artwork_types()) {
foreach (array_keys($types) as $type) {
$forms[$type . '_artwork_form']['callback'] = 'artwork_form';
}
}
return $forms;
}
[ 168 ]