$output.='<dd>'.t('<em>Simple actions</em> do not require configuration and are listed automatically as available on the <a href="!actions">Actions page</a>.',array('!actions'=>\Drupal::url('action.admin'))).'</dd>';
$output.='<dd>'.t('<em>Simple actions</em> do not require configuration and are listed automatically as available on the <a href="!actions">Actions page</a>.',array('!actions'=>\Drupal::url('entity.action.collection'))).'</dd>';
$output.='<dt>'.t('Creating and configuring advanced actions').'</dt>';
$output.='<dd>'.t('<em>Advanced actions</em> are user-created and have to be configured individually. Create an advanced action on the <a href="!actions">Actions page</a> by selecting an action type from the drop-down list. Then configure your action, for example by specifying the recipient of an automated email message.',array('!actions'=>\Drupal::url('action.admin'))).'</dd>';
$output.='<dd>'.t('<em>Advanced actions</em> are user-created and have to be configured individually. Create an advanced action on the <a href="!actions">Actions page</a> by selecting an action type from the drop-down list. Then configure your action, for example by specifying the recipient of an automated email message.',array('!actions'=>\Drupal::url('entity.action.collection'))).'</dd>';
$output.='</dl>';
return$output;
case'action.admin':
case'entity.action.collection':
$output='<p>'.t('There are two types of actions: simple and advanced. Simple actions do not require any additional configuration and are listed here automatically. Advanced actions need to be created and configured before they can be used because they have options that need to be specified; for example, sending an email to a specified address or unpublishing content containing certain words. To create an advanced action, select the action from the drop-down list in the advanced action section below and click the <em>Create</em> button.').'</p>';
return$output;
...
...
@@ -45,5 +45,6 @@ function action_entity_type_build(array &$entity_types) {
@@ -17,21 +17,21 @@ function block_content_help($route_name, RouteMatchInterface $route_match) {
case'help.page.block_content':
$output='';
$output.='<h3>'.t('About').'</h3>';
$output.='<p>'.t('The Custom Block module allows you to create blocks of content, which can be placed in regions throughout the website. Custom blocks can have fields; see the <a href="!field-help">Field module help</a> for more information. Once created, custom blocks can be placed like blocks provided by other modules; see the <a href="!blocks">Block module help page</a> for details. For more information, see <a href="!online-help">the online documentation for the Custom Block module</a>.',array('!block-content'=>\Drupal::url('block_content.list'),'!field-help'=>\Drupal::url('help.page',array('name'=>'field')),'!blocks'=>\Drupal::url('help.page',array('name'=>'block')),'!online-help'=>'https://drupal.org/documentation/modules/block_content')).'</p>';
$output.='<p>'.t('The Custom Block module allows you to create blocks of content, which can be placed in regions throughout the website. Custom blocks can have fields; see the <a href="!field-help">Field module help</a> for more information. Once created, custom blocks can be placed like blocks provided by other modules; see the <a href="!blocks">Block module help page</a> for details. For more information, see <a href="!online-help">the online documentation for the Custom Block module</a>.',array('!block-content'=>\Drupal::url('entity.block_content.collection'),'!field-help'=>\Drupal::url('help.page',array('name'=>'field')),'!blocks'=>\Drupal::url('help.page',array('name'=>'block')),'!online-help'=>'https://drupal.org/documentation/modules/block_content')).'</p>';
$output.='<h3>'.t('Uses').'</h3>';
$output.='<dl>';
$output.='<dt>'.t('Creating and managing custom block types').'</dt>';
$output.='<dd>'.t('Users with the <em>Administer blocks</em> permission can create different custom block types, each with different fields and display settings, from the <a href="!types">Custom block types</a> page. The Custom block types page lists all of your created custom block types, and allows you to edit and manage them. For more information about managing fields and display settings, see the <a href="!field-ui">Field UI module help</a>.',array('!types'=>\Drupal::url('block_content.type_list'),'!field-ui'=>\Drupal::url('help.page',array('name'=>'field_ui')))).'</dd>';
$output.='<dd>'.t('Users with the <em>Administer blocks</em> permission can create different custom block types, each with different fields and display settings, from the <a href="!types">Custom block types</a> page. The Custom block types page lists all of your created custom block types, and allows you to edit and manage them. For more information about managing fields and display settings, see the <a href="!field-ui">Field UI module help</a>.',array('!types'=>\Drupal::url('entity.block_content_type.collection'),'!field-ui'=>\Drupal::url('help.page',array('name'=>'field_ui')))).'</dd>';
$output.='<dd>'.t('Users with the <em>Administer blocks</em> permission can <a href="!block-add">add custom blocks</a> of each of their defined custom block types. Created custom blocks are then listed on the <a href="!blocks">Blocks administration page</a>.',array('!blocks'=>\Drupal::url('block.admin_display'),'!block-add'=>\Drupal::url('block_content.add_page'))).'</dd>';
$output.='</dl>';
return$output;
case'block_content.list':
case'entity.block_content.collection':
$output='<p>'.t('This page lists user-created blocks. These blocks are derived from block types. A block type can consist of different fields and display settings. From the block types tab you can manage these fields as well as create new block types.').'</p>';
return$output;
case'block_content.type_list':
case'entity.block_content_type.collection':
$output='<p>'.t('This page lists block types. A block type can consist of different fields and display settings. From here you can manage these fields as well as create new block types.').'</p>';
@@ -69,7 +69,7 @@ function comment_help($route_name, RouteMatchInterface $route_match) {
$output.='<h3>'.t('Uses').'</h3>';
$output.='<dl>';
$output.='<dt>'.t('Enabling commenting and configuring defaults').'</dt>';
$output.='<dd>'.t('Comment functionality can be enabled for any entity sub-type (for example, a <a href="!content-type">content type</a>). On the Manage fields page for each entity sub-type, you can enable commenting by adding a Comments field. The entity sub-types each have their own default comment settings configured as: <em>Open</em> to allow new comments, <em>Closed</em> to view existing comments, but prevent new comments, or <em>Hidden</em> to hide existing comments and prevent new comments. For background information about entities, see the <a href="!field">Field module help page</a>.',array('!content-type'=>\Drupal::url('node.overview_types'),'!field'=>\Drupal::url('help.page',array('name'=>'field')))).'</dd>';
$output.='<dd>'.t('Comment functionality can be enabled for any entity sub-type (for example, a <a href="!content-type">content type</a>). On the Manage fields page for each entity sub-type, you can enable commenting by adding a Comments field. The entity sub-types each have their own default comment settings configured as: <em>Open</em> to allow new comments, <em>Closed</em> to view existing comments, but prevent new comments, or <em>Hidden</em> to hide existing comments and prevent new comments. For background information about entities, see the <a href="!field">Field module help page</a>.',array('!content-type'=>\Drupal::url('entity.node_type.collection'),'!field'=>\Drupal::url('help.page',array('name'=>'field')))).'</dd>';
$output.='<dd>'.t('When you create an entity item, you can override the default comment settings. Changing the entity sub-type defaults will not affect existing entity items, whether they used the default settings or had overrides.').'</dd>';
$output.='<dt>'.t('Approving and managing comments').'</dt>';
...
...
@@ -77,7 +77,7 @@ function comment_help($route_name, RouteMatchInterface $route_match) {
$output.='</dl>';
return$output;
case'comment.type_list':
case'entity.comment_type.collection':
$output='<p>'.t('This page provides a list of all comment types on the site and allows you to manage the fields, form and display settings for each.').'</p>';
$output.='<dd>'.t('In order to translate configuration, the website must have at least two <a href="!url">languages</a>.',array('!url'=>\Drupal::url('language.admin_overview'))).'</dd>';
$output.='<dd>'.t('In order to translate configuration, the website must have at least two <a href="!url">languages</a>.',array('!url'=>\Drupal::url('entity.configurable_language.collection'))).'</dd>';
$output.='<dd>'.t('Users with the <em>Translate user edited configuration</em> permission can access the configuration translation overview, and manage translations for specific languages. The <a href="!translation-page">Configuration translation</a> page shows a list of all configuration text that can be translated, either as individual items or as lists. After you click on <em>Translate</em>, you are provided with a list of all languages. You can <em>add</em> or <em>edit</em> a translation for a specific language. Users with specific configuration permissions can also <em>edit</em> the text for the site\'s default language. For some configuration text items (for example for the site information), the specific translation pages can also be accessed directly from their configuration pages.',array('!translation-page'=>\Drupal::url('config_translation.mapper_list'))).'</dd>';
$output.='<dt>'.t('Translating date formats').'</dt>';
$output.='<dd>'.t('The <a href="@contact">Contact page</a> provides a simple form for users with the <em>Use the site-wide contact form</em> permission to send comments, feedback, or other requests. You can create forms for directing the contact messages to a set of defined recipients. Common forms for a business site, for example, might include "Website feedback" (messages are forwarded to website administrators) and "Product information" (messages are forwarded to members of the sales department). Email addresses defined within a form are not displayed publicly.',array('@contact'=>\Drupal::url('contact.site_page'))).'</p>';
$output.='<dt>'.t('Navigation').'</dt>';
$output.='<dd>'.t('When the site-wide contact form is enabled, a link in the <em>Footer</em> menu is created, which you can modify on the <a href="@menu">Menus administration page</a>.',array('@menu'=>\Drupal::url('menu_ui.overview_page'))).'</dd>';
$output.='<dd>'.t('When the site-wide contact form is enabled, a link in the <em>Footer</em> menu is created, which you can modify on the <a href="@menu">Menus administration page</a>.',array('@menu'=>\Drupal::url('entity.menu.collection'))).'</dd>';
$output.='<dt>'.t('Customization').'</dt>';
$output.='<dd>'.t('If you would like additional text to appear on the site-wide or personal contact page, use a block. You can create and edit blocks on the <a href="@blocks">Blocks administration page</a>.',array('@blocks'=>\Drupal::url('block.admin_display'))).'</dd>';
$output.='</dl>';
return$output;
case'contact.form_list':
case'entity.contact_form.collection':
$output='<p>'.t('Add one or more forms on this page to set up your site-wide <a href="@form">contact form</a>.',array('@form'=>\Drupal::url('contact.site_page'))).'</p>';
$output.='<p>'.t('A <em>Contact</em> menu item is added to the <em>Footer</em> menu, which you can modify on the <a href="@menu-settings">Menus administration page</a>.',array('@menu-settings'=>\Drupal::url('menu_ui.overview_page'))).'</p>';
$output.='<p>'.t('A <em>Contact</em> menu item is added to the <em>Footer</em> menu, which you can modify on the <a href="@menu-settings">Menus administration page</a>.',array('@menu-settings'=>\Drupal::url('entity.menu.collection'))).'</p>';
$output.='<p>'.t('If you would like additional text to appear on the site-wide contact page, use a block. You can create and edit blocks on the <a href="@blocks">Blocks administration page</a>.',array('@blocks'=>\Drupal::url('block.admin_display'))).'</p>';
$output.='<dd>'.t('In order to translate content, the website must have at least two <a href="!url">languages</a>. When that is the case, you can enable translation for the desired content entities on the <a href="!translation-entity">Content language</a> page. When enabling translation you can choose the default language for content and decide whether to show the language selection field on the content editing forms.',array('!url'=>\Drupal::url('language.admin_overview'),'!translation-entity'=>\Drupal::url('language.content_settings_page'),'!language-help'=>\Drupal::url('help.page',array('name'=>'language')))).'</dd>';
$output.='<dd>'.t('In order to translate content, the website must have at least two <a href="!url">languages</a>. When that is the case, you can enable translation for the desired content entities on the <a href="!translation-entity">Content language</a> page. When enabling translation you can choose the default language for content and decide whether to show the language selection field on the content editing forms.',array('!url'=>\Drupal::url('entity.configurable_language.collection'),'!translation-entity'=>\Drupal::url('language.content_settings_page'),'!language-help'=>\Drupal::url('help.page',array('name'=>'language')))).'</dd>';
$output.='<dt>'.t('Enabling field translation').'</dt>';
$output.='<dd>'.t('You can define which fields of a content entity can be translated. For example, you might want to translate the title and body field while leaving the image field untranslated. If you exclude a field from being translated, it will still show up in the content editing form, but any changes made to that field will be applied to <em>all</em> translations of that content.').'</dd>';
$output.='<dt>'.t('Translating content').'</dt>';
...
...
@@ -40,7 +40,7 @@ function content_translation_help($route_name, RouteMatchInterface $route_match)
$output.='<br/>'.t('Before you can translate content, there must be at least two languages added on the <a href="!url">languages administration</a> page.',array('!url'=>\Drupal::url('language.admin_overview')));
$output.='<br/>'.t('Before you can translate content, there must be at least two languages added on the <a href="!url">languages administration</a> page.',array('!url'=>\Drupal::url('entity.configurable_language.collection')));
@@ -39,7 +39,7 @@ function datetime_help($route_name, RouteMatchInterface $route_match) {
$output.='<dt>'.t('Managing and displaying date fields').'</dt>';
$output.='<dd>'.t('The <em>settings</em> and the <em>display</em> of the Date field can be configured separately. See the <a href="!field_ui">Field UI help</a> for more information on how to manage fields and their display.',array('!field_ui'=>\Drupal::url('help.page',array('name'=>'field_ui')))).'</dd>';
$output.='<dt>'.t('Displaying dates').'</dt>';
$output.='<dd>'.t('Dates can be displayed using the <em>Plain</em> or the <em>Default</em> formatter. The <em>Plain</em> formatter displays the date in the <a href="http://en.wikipedia.org/wiki/ISO_8601">ISO 8601</a> format. If you choose the <em>Default</em> formatter, you can choose a format from a predefined list that can be managed on the <a href="!date_format_list">Date and time formats</a> page.',array('!date_format_list'=>\Drupal::url('system.date_format_list'))).'</dd>';
$output.='<dd>'.t('Dates can be displayed using the <em>Plain</em> or the <em>Default</em> formatter. The <em>Plain</em> formatter displays the date in the <a href="http://en.wikipedia.org/wiki/ISO_8601">ISO 8601</a> format. If you choose the <em>Default</em> formatter, you can choose a format from a predefined list that can be managed on the <a href="!date_format_list">Date and time formats</a> page.',array('!date_format_list'=>\Drupal::url('entity.date_format.collection'))).'</dd>';
