--- field_ui_orig.module 2010-01-29 22:14:17.000000000 -0600
+++ field_ui.module 2010-02-02 11:25:35.000000000 -0600
@@ -13,15 +13,26 @@ function field_ui_help($path, $arg) {
switch ($path) {
case 'admin/help#field_ui':
$output = '';
- $output .= '' . t('About') . '
';
- $output .= '' . t('The Field UI module provides an administrative user interface (UI) for adding custom fields to content types, users, comments, and other types of data. The field types are defined by other modules, and collected and managed by the Field module. For more information, see the online handbook entry for Field UI module.', array('@field-ui' => 'http://drupal.org/handbook/modules/field-ui', '@field' => url('admin/help/field'))) . '
';
- $output .= '' . t('Uses') . '
';
- $output .= '';
- $output .= '- ' . t('Defining custom fields') . '
';
- $output .= '- ' . t('When adding a custom field, you need to determine whether the field type will contain text, numbers, lists, etc., as well as how it will be input (as a text field, text area, select box, checkboxes, radio buttons, etc.). A field may have a single value or multiple values. For example, an employee field might have a single employee identification number, whereas a phone number field might have multiple phone numbers.') . '
';
- $output .= '- ' . t('Adding fields to content types') . '
';
- $output .= '- ' . t("Some fields are provided by default when you create a content type, such as the Title and Body fields. The Field UI module lets administrators edit or delete the default fields attached to content, as well as create new fields for storing any additional information. Field configuration is accessible through tabs on each specific content type's configuration page, listed on the Content types administration page. See the Node module help page for more information about content types.", array('@content-types' => url('admin/structure/types'), '@node-help' => url('admin/help/node'))) . '
';
- $output .= '
';
+$output .= '' . t('About') . '
';
+$output .= '' . t('The Field UI module provides an administrative user interface (UI) for managing custom fields on content types, taxonomy terms, user accounts, comments, and other data. For example, the Article content type created by the Default install profile has the fields Title, Image, Body, and Tags. Field types are defined by other modules, and collected and managed by the Field module. For more information, see the online handbook entry for Field UI module.', array('@field' => url('admin/help/field'), '@field_ui' => 'http://drupal.org/handbook/modules/field-ui')) . '
';
+$output .= '' . t('Uses') . '
';
+$output .= '';
+$output .= '- ' . t(' Planning custom fields') . '
';
+$output .= '- ' . t('What the field will be called. Choose the name that is displayed in the Drupal user interface (its label) and the name stored in the database. The label can be changed later if needed, but name stored in the database cannot.') . '
';
+$output .= '- ' . t("What data the field will store. Choose what kind of data the field will contain (text, a number, a file, etc. — the field type), how it will be input (text field, select box, radio buttons, etc. — the field's widget), and how it will be shown when viewed (the field's display). The widget and display can be changed later, but the field type cannot.") . '
';
+$output .= '- ' . t("How many values the field will store. Chooose whether the field will store a single value or multiple values. For example, an employee identification number field might store a single number, whereas a phone number field might store multiple phone numbers. This setting can be changed after you've created the field, but if you reduce the number of values stored, any values beyond the number you've set will be lost.") . '
';
+$output .= '- ' . t('Reusing custom fields') . '
';
+$output .= '- ' . t('When adding a custom field, you can create a new one or reuse a previously defined field. For example, if you reuse an image field, all the image files are stored in the same directory (and displayed in the same way) everywhere the field is used. For example, the Title and Body fields are shared by the Article and Page content types provided by the Default install profile.') . '
';
+$output .= '- ' . t('Some settings of a reused field are unique to that occurrence of the field; others are shared across all occurrences. For example, the label of a text field is unique to each item that uses the text field. The "number of values" setting is shared, meaning that changing it on one occurrence of the field changes that setting everywhere else it is used.') . '
';
+$output .= '- ' . t('Adding fields to content types') . '
';
+$output .= '- ' . t('Manage the fields of a content type on the "manage fields" page of a content type. Some fields (e.g. Title and Body) are provided by the Default install profile when creating a content type.', array('@types' => url('admin/structure/types'))) . '
';
+$output .= '- ' . t('Adding fields to taxonomy terms') . '
';
+$output .= '- ' . t('Manage the fields of a taxonomy vocabulary on the "manage fields" page of a vocabulary. Fields are used by each term in that vocabulary. For example, you could add an image field to store an icon with each term.', array('@taxonomy' => url('admin/structure/taxonomy'))) . '
';
+$output .= '- ' . t('Adding fields to user accounts') . '
';
+$output .= '- ' . t('Manage the fields for user accounts on the manage fields page of Account settings. For example, you could add a long text field to allow users to include a biography.', array('@fields' => url('admin/config/people/accounts/fields'), '@accounts' => url('admin/config/people/accounts'))) . '
';
+$output .= '- ' . t('Adding fields to comments') . '
';
+$output .= '- ' . t('Manage the fields for comments on the "comment fields" page of a content types. Different content types can have different sets of fields for their comments. For example, you could add a website field to allow commenters to add a link to their website.', array('@types' => url('admin/structure/types'))) . '
';
+$output .= '
';
return $output;
case 'admin/reports/fields':