function content_help in Content Construction Kit (CCK) 6

Same name and namespace in other branches

1. 5 content.module \content_help()
2. 6.3 content.module \content_help()
3. 6.2 content.module \content_help()

File

./content.module, line 21

Allows administrators to associate custom fields to content types.

Code

function content_help($path, $arg) {
  switch ($path) {
    case 'admin/help#content':
      $output = '<p>' . t('The content module, a required component of the Content Construction Kit (CCK), allows administrators to associate custom fields with content types. In Drupal, content types are used to define the characteristics of a post, including the title and description of the fields displayed on its add and edit pages. Using the content module (and the other helper modules included in CCK), custom fields beyond the default "Title" and "Body" may be added. CCK features are accessible through tabs on the <a href="@content-types">content types administration page</a>. (See the <a href="@node-help">node module help page</a> for more information about content types.)', array(
        '@content-types' => url('admin/content/types'),
        '@node-help' => url('admin/help/node'),
      )) . '</p>';
      $output .= '<p>' . t('When adding a custom field to a content type, you determine its type (whether it will contain text, numbers, or references to other objects) and how it will be displayed (either as a text field or area, a select box, checkbox, radio button, or autocompleting field). A field may have multiple values (i.e., a "person" may have multiple e-mail addresses) or a single value (i.e., an "employee" has a single employee identification number). As you add and edit fields, CCK automatically adjusts the structure of the database as necessary. CCK also provides a number of other features, including intelligent caching for your custom data, an import and export facility for content type definitions, and integration with other contributed modules.') . '</p>';
      $output .= '<p>' . t('Custom field types are provided by a set of optional modules included with CCK (each module provides a different type). The <a href="@modules">modules page</a> allows you to enable or disable CCK components. A default installation of CCK includes:', array(
        '@modules' => url('admin/build/modules'),
      )) . '</p>';
      $output .= '<ul>';
      $output .= '<li>' . t('<em>number</em>, which adds numeric field types, in integer, decimal or floating point form. You may define a set of allowed inputs, or specify an allowable range of values. A variety of common formats for displaying numeric data are available.') . '</li>';
      $output .= '<li>' . t("<em>text</em>, which adds text field types. A text field may contain plain text only, or optionally, may use Drupal's input format filters to securely manage rich text input. Text input fields may be either a single line (text field), multiple lines (text area), or for greater input control, a select box, checkbox, or radio buttons. If desired, CCK can validate the input to a set of allowed values.") . '</li>';
      $output .= '<li>' . t('<em>nodereference</em>, which creates custom references between Drupal nodes. By adding a <em>nodereference</em> field and two different content types, for instance, you can easily create complex parent/child relationships between data (multiple "employee" nodes may contain a <em>nodereference</em> field linking to an "employer" node).') . '</li>';
      $output .= '<li>' . t('<em>userreference</em>, which creates custom references to your sites\' user accounts. By adding a <em>userreference</em> field, you can create complex relationships between your site\'s users and posts. To track user involvement in a post beyond Drupal\'s standard <em>Authored by</em> field, for instance, add a <em>userreference</em> field named "Edited by" to a content type to store a link to an editor\'s user account page.') . '</li>';
      $output .= '<li>' . t('<em>fieldgroup</em>, which creates collapsible fieldsets to hold a group of related fields. A fieldset may either be open or closed by default. The order of your fieldsets, and the order of fields within a fieldset, is managed via a drag-and-drop interface provided by content module.') . '</li>';
      $output .= '</ul>';
      $output .= '<p>' . t('For more information, see the online handbook entry for <a href="@handbook-cck">CCK</a> or the <a href="@project-cck">CCK project page</a>.', array(
        '@handbook-cck' => 'http://drupal.org/handbook/modules/cck',
        '@project-cck' => 'http://drupal.org/project/cck',
      )) . '</p>';
      return $output;
  }
  if (preg_match('!^admin/content/node-type/.*/display!', $path)) {
    if (preg_match('!^admin/content/node-type/.*/display$!', $path)) {
      return t("Configure how this content type's fields and field labels should be displayed when it's viewed in teaser and full-page mode.");
    }
    else {
      return t("Configure how this content type's fields should be displayed when it's rendered in the following contexts.");
    }
  }
  if (preg_match('!^admin/content/node-type/.*/fields$!', $path)) {
    return t('Control the order of fields in the input form.');
  }
}