Index: modules/field_ui/field_ui.module
===================================================================
RCS file: /cvs/drupal/drupal/modules/field_ui/field_ui.module,v
retrieving revision 1.23
diff -u -r1.23 field_ui.module
--- modules/field_ui/field_ui.module 30 Jan 2010 04:14:17 -0000 1.23
+++ modules/field_ui/field_ui.module 2 Feb 2010 21:39:17 -0000
@@ -14,13 +14,31 @@
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('The Field UI module provides an administrative user interface (UI) for attaching and managing custom fields on content types, taxonomy vocabularies, user accounts, comments, and other data. Fields can store various types of data, and the each type of data has a field type associated with it. 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('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('Planning a new custom field') . '
';
+ $output .= '- ' . t('There are several decisions you will need to make before creating a custom field:') . '
';
+ $output .= '- ' . t('What the field will be called') . '
';
+ $output .= '- ' . t('A field has a label (the name displayed in the user interface) and a machine name (the name stored in the database). The label can be changed after you create the field, if needed, but the machine name cannot be changed after you have created the field.') . '';
+ $output .= '
- ' . t('What type of data the field will store') . '
';
+ $output .= '- ' . t('Each field can store one type of data (text, number, file, etc.). When you define a field, you choose a particular field type, which corresponds to the type of data you want to store. The field type cannot be changed after you have created the field.') . '
';
+ $output .= '- ' . t('How the data will be input and displayed') . '
';
+ $output .= '- ' . t('Each field type has one or more available widgets associated with it; each widget provides a mechanism for data input when you are editing (text box, select list, file upload, etc.). Each field type also has one or more available display formatters, which determine how the field is displayed to site visitors. The widget and display formatter can be changed after you have created the field.') . '
';
+ $output .= '- ' . t('How many values the field will store') . '
';
+ $output .= '- ' . t('You can store one value, a specific number of values, or an unlimited number of values in each field. 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 have created the field, but if you reduce the number of values, you may lose information.') . '
';
+ $output .= '
';
+ $output .= ' - ' . t('Reusing custom fields') . '
';
+ $output .= '- ' . t('Once you have created a custom field, you can reuse it. For example, if you create a custom image field on one content type, and you need to have an image field with the same parameters on another content type, you can add the same field you have already created to the second content type. You can also add this field to a taxonomy vocabulary, comments, user accounts, etc.') . '
';
+ $output .= '- ' . t('Some settings of a reused field are unique to each use of the field; others are shared across all places you use the field. For example, the label of a text field is unique to each use, while the setting for the number of values is shared.') . '
';
$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 .= '- ' . t('Manage the fields of a content type on the Manage fields tab of the content type edit page, which you can reach from the Content types page. When you add a field to a content type, each content item of that type you create will have that field. Some fields, such as the Title and Body, are provided for you when you create a content type, or are provided on content types created by your installation profile.', array('@types' => url('admin/structure/types'))) . '
';
+ $output .= '- ' . t('Adding fields to taxonomy vocabularies') . '
';
+ $output .= '- ' . t('Manage the fields of a taxonomy vocabulary on the Manage fields tab of the vocabulary edit page, which you can reach from the Taxonomy page. When you add a field to a vocabulary, each term in that vocabulary will have that field. For example, you could add an image field to a vocabulary 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 users on the Manage fields tab of the Account settings page. When you add a field to user accounts, each user account will have that field. 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 associated with a particular content type on the Comment fields tab of the content type edit page (you can edit content types using links on the Content types page). The comment fields for each content type are managed separately. When you add a field to comments on a particular content type, each comment on a content item of that type will have that field. For example, you could add a website field to the comments on forum posts, to allow forum commenters to add a link to their website.', array('@types' => url('admin/structure/types'))) . '
';
$output .= '
';
return $output;