diff --git a/core/modules/field_ui/field_ui.module b/core/modules/field_ui/field_ui.module index 24e5221..631465e 100644 --- a/core/modules/field_ui/field_ui.module +++ b/core/modules/field_ui/field_ui.module @@ -18,33 +18,23 @@ function field_ui_help($path, $arg) { case 'admin/help#field_ui': $output = ''; $output .= '

' . t('About') . '

'; - $output .= '

' . t('The Field UI module provides an administrative user interface (UI) for attaching and managing fields. Fields can be defined at the content-type level for content items and comments, at the vocabulary level for taxonomy terms, and at the site level for user accounts. Other modules may also enable fields to be defined for their data. Field types (text, image, number, etc.) are defined by 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/documentation/modules/field-ui')) . '

'; + $output .= '

' . t('The Field UI module provides an administrative user interface (UI) for managing and displaying fields. Fields can be attached to most entities. Different field types, input widgets and display formats (for example for text, number or file fields) are provided by the modules enabled on your site, and managed by the Field module. For more information on fields and entities, see the Field module and Entity module help pages. For more information, see the online documentation for the Field UI module.', array('@field' => url('admin/help/field'), '!field_ui_docs' => 'https://drupal.org/documentation/modules/field-ui')) . '

'; $output .= '

' . t('Uses') . '

'; $output .= '
'; - $output .= '
' . t('Planning fields') . '
'; - $output .= '
' . t('There are several decisions you will need to make before defining a field for content, comments, etc.:') . '
'; - $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 used internally). 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 display options, which determine how the field is displayed to site visitors. The widget and display options 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 maximum 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 maximum number of values, you may lose information.') . '
'; - $output .= '
'; - $output .= '
' . t('Reusing fields') . '
'; - $output .= '
' . t('Once you have defined a field, you can reuse it. For example, if you define a custom image field for 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 to the second content type, in the Re-use existing field area of the user interface. You could 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('There are two main reasons for reusing fields. First, reusing fields can save you time over defining new fields. Second, reusing fields also allows you to display, filter, group, and sort content together by field across content types. For example, the contributed Views module allows you to create lists and tables of content. So if you use the same field on multiple content types, you can create a View containing all of those content types together displaying that field, sorted by that field, and/or filtered by that field.') . '
'; - $output .= '
' . t('Fields on content items') . '
'; - $output .= '
' . t('Fields on content items are defined at the content-type level, on the Manage fields tab of the content type edit page (which you can reach from the Content types page). When you define a field for a content type, each content item of that type will have that field added to it. 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('Fields on taxonomy terms') . '
'; - $output .= '
' . t('Fields on taxonomy terms are defined at the taxonomy vocabulary level, on the Manage fields tab of the vocabulary edit page (which you can reach from the Taxonomy page). When you define a field for a vocabulary, each term in that vocabulary will have that field added to it. For example, you could define an image field for a vocabulary to store an icon with each term.', array('@taxonomy' => url('admin/structure/taxonomy'))) . '
'; - $output .= '
' . t('Fields on user accounts') . '
'; - $output .= '
' . t('Fields on user accounts are defined on a site-wide basis on the Manage fields tab of the Account settings page. When you define a field for user accounts, each user account will have that field added to it. 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('Fields on comments') . '
'; - $output .= '
' . t('Fields on comments are defined at the content-type level, on the Comment fields tab of the content type edit page (which you can reach from the Content types page). When you add a field for comments, each comment on a content item of that type will have that field added to it. 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 .= '
'; + $output .= '
' . t('Creating a field') . '
'; + $output .= '
' . t('You can attach fields to most entities on your site. This includes for example content types, taxonomy terms and user profile accounts. You can add new fields on the Manage fields page of an entity. When you add a Label text, then a machine name is automatically generated, by you can change it during the creation of a new field by clicking on the Edit link next to it. Once the field is created you cannot change the machine name anymore. You need to choose a Field type from the drop-down list. After clicking on Save, you can configure the Field settings on a separate page. These settings can for example include how many values can be filled into the field, or where files are stored, and thhey apply to the field everywhere it is used on your site. They impact the way the data for this field is stored in the database and therefore cannot be changed anymore once the field has been created.') . '
'; + $output .= '
' . t('Configuring a field for an entity') . '
'; + $output .= '
' . t('During the creation of a field, you can also configure the Settings for your field used with this specific entity. This includes for example the label, whether the field is required and other options depending on the field type. You return to these settings by choosing Edit on the Manage fields page of your entity.') . '
'; + $output .= '
' . t('Configuring a field in a form') . '
'; + $output .= '
' . t('On the Manage form display page of your entity, you can configure how each field is displayed to the users on the content creation pages. Depending on the field type, one or several widgets are available that allow you to configure the field further. The configuration options can for example include the size of a text field, or placeholder text that is displayed in the form field until a user has entered text there. You can also change the order in which the fields are displayed in the form. You can exclude a field from a form by choosing Hidden from the widget drop-down list, or by dragging it into the Disabled section.') . '
'; + $output .= '
' . t('Configuring the display of a field') . '
'; + $output .= '
' . t('On the Manage display page of your entity, you can configure how each field is displayed by default and in different display modes (for example in a teaser or as a search result). You can toggle between the displays at the top of the page, and you can add additional ones by enabling them in the Custom display settings. You can choose whether and how to display the label of the field from the Label drop-down list. Depending on the field type, one or several formats are available that allow you to configure the display of the field further. You can also change the order in which the fields are displayed. You exclude a field from a specific display, by choosing Hidden as format, or by dragging it into the Disabled section.') . '
'; + $output .= '
' . t('Re-using fields ') . '
'; + $output .= '
' . t('Once you have created a field you can re-use it with other entities by choosing it from the drop-down list Select an existing field on the Manage fields page of that enity. (This list is not displayed if there are no fields available that could be re-used.) You also need to specify the label text for the field used with this entity. Once an existing field has been attached to your entity, you can edit its settings, its form display and its display, but not the field settings (see above).') . '
'; + $output .= '
' . t('Listing all fields') . '
'; + $output .= '
' . t('All fields are listed on the Field list pages. On the Entities field list, all fields are listed with name, type and linked to the entities with which they are used. If the Views and Views UI modules are enabled, and a field is used in a view, then it is listed on the Used in views page, with a link to the specific view.' , array('!entity-list' => \Drupal::url('field_ui.list'), '!views-list' => (\Drupal::moduleHandler()->moduleExists('views_ui')) ? \Drupal::url('views_ui.reports_fields') : '#', '!views' => (\Drupal::moduleHandler()->moduleExists('views')) ? \Drupal::url('help.page', array('name' => 'views')) : '#','!views-ui' => (\Drupal::moduleHandler()->moduleExists('views_ui')) ? \Drupal::url('help.page', array('name' => 'views_ui')) : '#')) . '
'; + + return $output; case 'admin/reports/fields':