Security update for Core, with self-updated composer

[yaffs-website] / web / core / modules / taxonomy / taxonomy.module

diff --git a/web/core/modules/taxonomy/taxonomy.module b/web/core/modules/taxonomy/taxonomy.module
index 4a93989ad52fe5817449598730c5baec9706e75f..e17346ba830315fe5d150ca73df8b28b2d31b058 100644 (file)
--- a/web/core/modules/taxonomy/taxonomy.module
+++ b/web/core/modules/taxonomy/taxonomy.module
@@ -22,6 +22,8 @@ use Drupal\taxonomy\VocabularyInterface;
  *
  * @deprecated in Drupal 8.2.x and will be removed before 9.0.0. Use
  *   \Drupal\taxonomy\VocabularyInterface::HIERARCHY_DISABLED instead.
+ *
+ * @see https://www.drupal.org/node/2807795
  */
 const TAXONOMY_HIERARCHY_DISABLED = 0;
 
@@ -30,6 +32,8 @@ const TAXONOMY_HIERARCHY_DISABLED = 0;
  *
  * @deprecated in Drupal 8.2.x and will be removed before 9.0.0. Use
  *   \Drupal\taxonomy\VocabularyInterface::HIERARCHY_SINGLE instead.
+ *
+ * @see https://www.drupal.org/node/2807795
  */
 const TAXONOMY_HIERARCHY_SINGLE = 1;
 
@@ -38,6 +42,8 @@ const TAXONOMY_HIERARCHY_SINGLE = 1;
  *
  * @deprecated in Drupal 8.2.x and will be removed before 9.0.0. Use
  *   \Drupal\taxonomy\VocabularyInterface::HIERARCHY_MULTIPLE instead.
+ *
+ * @see https://www.drupal.org/node/2807795
  */
 const TAXONOMY_HIERARCHY_MULTIPLE = 2;
 
@@ -61,7 +67,7 @@ function taxonomy_help($route_name, RouteMatchInterface $route_match) {
       $output .= '<dt>' . t('Classifying entity content') . '</dt>';
       $output .= '<dd>' . t('A user with the <em>Administer fields</em> permission for a certain entity type may add <em>Taxonomy term</em> reference fields to the entity type, which will allow entities to be classified using taxonomy terms. See the <a href=":entity_reference">Entity Reference help</a> for more information about reference fields. See the <a href=":field">Field module help</a> and the <a href=":field_ui">Field UI help</a> pages for general information on fields and how to create and manage them.', [':field_ui' => $field_ui_url, ':field' => \Drupal::url('help.page', ['name' => 'field']), ':entity_reference' => \Drupal::url('help.page', ['name' => 'entity_reference'])]) . '</dd>';
       $output .= '<dt>' . t('Adding new terms during content creation') . '</dt>';
-      $output .= '<dd>' . t('Allowing users to add new terms gradually builds a vocabulary as content is added and edited. Users can add new terms if either of the two <em>Autocomplete</em> widgets is chosen for the Taxonomy term reference field in the <em>Manage form display</em> page for the field. You will also need to enable the <em>Create referenced entities if they don\'t already exist</em> option, and restrict the field to one vocabulary.') . '</dd>';
+      $output .= '<dd>' . t("Allowing users to add new terms gradually builds a vocabulary as content is added and edited. Users can add new terms if either of the two <em>Autocomplete</em> widgets is chosen for the Taxonomy term reference field in the <em>Manage form display</em> page for the field. You will also need to enable the <em>Create referenced entities if they don't already exist</em> option, and restrict the field to one vocabulary.") . '</dd>';
       $output .= '<dt>' . t('Configuring displays and form displays') . '</dt>';
       $output .= '<dd>' . t('See the <a href=":entity_reference">Entity Reference help</a> page for the field widgets and formatters that can be configured for any reference field on the <em>Manage display</em> and <em>Manage form display</em> pages. Taxonomy additionally provides an <em>RSS category</em> formatter that displays nothing when the entity item is displayed as HTML, but displays an RSS category instead of a list when the entity item is displayed in an RSS feed.', [':entity_reference' => \Drupal::url('help.page', ['name' => 'entity_reference'])]) . '</li>';
       $output .= '</ul>';