function text_field_settings in Content Construction Kit (CCK) 6

Same name in this branch

1. 6 examples/simple_field.php \text_field_settings()
2. 6 examples/example_field.php \text_field_settings()
3. 6 modules/text/text.module \text_field_settings()

Same name and namespace in other branches

1. 5 text.module \text_field_settings()
2. 6.3 modules/text/text.module \text_field_settings()
3. 6.2 modules/text/text.module \text_field_settings()

Implementation of hook_field_settings().

Handle the settings for a field.

Parameters

$op: The operation to be performed. Possible values:

• "form": Display the field settings form.
• "validate": Check the field settings form for errors.
• "save": Declare which fields to save back to the database.
• "database columns": Declare the columns that content.module should create and manage on behalf of the field. If the field module wishes to handle its own database storage, this should be omitted.
• "filters": Declare the Views filters available for the field. (this is used in CCK's default Views tables definition) They always apply to the first column listed in the "database columns" array.

$field: The field on which the operation is to be performed.

Return value

This varies depending on the operation.

• "form": an array of form elements to add to the settings page.
• "validate": no return value. Use form_set_error().
• "save": an array of names of form elements to be saved in the database.
• "database columns": an array keyed by column name, with arrays of column information as values. This column information must include "type", the MySQL data type of the column, and may also include a "sortable" parameter to indicate to views.module that the column contains ordered information. TODO : Details of other information that can be passed to the database layer can be found in the API for the Schema API.
• "filters": an array of 'filters' definitions as expected by views.module (see Views Documentation). When providing several filters, it is recommended to use the 'name' attribute in order to let the user distinguish between them. If no 'name' is specified for a filter, the key of the filter will be used instead.

File

examples/simple_field.php, line 157

SIMPLE EXAMPLE. This is similar to to example_field but creates only a single widget formatted in the traditional manner, not using hook_elements. This example also omits all optional parts of the field module to create a simpler example for…

Code

function text_field_settings($op, $field) {
  switch ($op) {
    case 'form':
      $form = array();
      $form['max_length'] = array(
        '#type' => 'textfield',
        '#title' => t('Maximum length'),
        '#default_value' => is_numeric($field['max_length']) ? $field['max_length'] : '',
        '#required' => FALSE,
        '#description' => t('The maximum length of the field in characters. Leave blank for an unlimited size.'),
      );
      return $form;
    case 'save':
      return array(
        'max_length',
      );
    case 'database columns':
      $columns['value'] = array(
        'type' => 'varchar',
        'length' => $field['max_length'],
        'not null' => FALSE,
        'sortable' => TRUE,
      );
      return $columns;
    case 'filters':
      return array(
        'like' => array(
          'operator' => 'views_handler_operator_like',
          'handler' => 'views_handler_filter_like',
        ),
      );
      break;
  }
}