moduleExists('field_ui') ? Url::fromRoute('help.page', ['name' => 'field_ui'])->toString() : '#'; $output = ''; $output .= '

' . $this->t('About') . '

'; $output .= '

' . $this->t('The Taxonomy module allows users who have permission to create and edit content to categorize (tag) content of that type. Users who have the Administer vocabularies and terms permission can add vocabularies that contain a set of related terms. The terms in a vocabulary can either be pre-set by an administrator or built gradually as content is added and edited. Terms may be organized hierarchically if desired.', [ ':permissions' => Url::fromRoute('user.admin_permissions.module', [ 'modules' => 'taxonomy', ])->toString(), ]) . '

'; $output .= '

' . $this->t('For more information, see the online documentation for the Taxonomy module.', [':taxonomy' => 'https://www.drupal.org/docs/8/core/modules/taxonomy']) . '

'; $output .= '

' . $this->t('Uses') . '

'; $output .= '

' . $this->t('Managing vocabularies') . ': ' . $this->t('Users who have the Administer vocabularies and terms permission can add and edit vocabularies from the Taxonomy administration page. Vocabularies can be deleted from their Edit vocabulary page. Users with the Taxonomy term: Administer fields permission may add additional fields for terms in that vocabulary using the Field UI module.', [ ':taxonomy_admin' => Url::fromRoute('entity.taxonomy_vocabulary.collection')->toString(), ':field_ui' => $field_ui_url, ]) . '
' . $this->t('Managing terms') . ': ' . $this->t('Users who have the Administer vocabularies and terms permission or the Edit terms permission for a particular vocabulary can add, edit, and organize the terms in a vocabulary from a vocabulary\'s term listing page, which can be accessed by going to the Taxonomy administration page and clicking List terms in the Operations column. Users must have the Administer vocabularies and terms permission or the Delete terms permission for a particular vocabulary to delete terms.', [ ':taxonomy_admin' => Url::fromRoute('entity.taxonomy_vocabulary.collection')->toString(), ]) . '
' . $this->t('Classifying entity content') . ': ' . $this->t('A user with the Administer fields permission for a certain entity type may add Taxonomy term reference fields to the entity type, which will allow entities to be classified using taxonomy terms. See the Entity Reference help for more information about reference fields. See the Field module help and the Field UI help pages for general information on fields and how to create and manage them.', [ ':field_ui' => $field_ui_url, ':field' => Url::fromRoute('help.page', [ 'name' => 'field', ])->toString(), ':entity_reference' => Url::fromRoute('help.page', [ 'name' => 'entity_reference', ])->toString(), ]) . '
' . $this->t('Adding new terms during content creation') . ': ' . $this->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 Autocomplete widgets is chosen for the Taxonomy term reference field in the Manage form display page for the field. You will also need to enable the Create referenced entities if they don't already exist option, and restrict the field to one vocabulary.") . '
' . $this->t('Configuring displays and form displays') . ': ' . $this->t('See the Entity Reference help page for the field widgets and formatters that can be configured for any reference field on the Manage display and Manage form display pages. Taxonomy additionally provides an RSS category 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' => Url::fromRoute('help.page', [ 'name' => 'entity_reference', ])->toString(), ]) . ''; $output .= ''; $output .= '

'; return $output; case 'entity.taxonomy_vocabulary.collection': $output = '

' . $this->t('Taxonomy is for categorizing content. Terms are grouped into vocabularies. For example, a vocabulary called "Fruit" would contain the terms "Apple" and "Banana".') . '

'; return $output; } return NULL; } /** * Implements hook_theme(). */ #[Hook('theme')] public function theme() : array { return ['taxonomy_term' => ['render element' => 'elements']]; } /** * Implements hook_local_tasks_alter(). * * @todo Evaluate removing as part of https://www.drupal.org/node/2358923. */ #[Hook('local_tasks_alter')] public function localTasksAlter(&$local_tasks): void { $local_task_key = 'config_translation.local_tasks:entity.taxonomy_vocabulary.config_translation_overview'; if (isset($local_tasks[$local_task_key])) { // The config_translation module expects the base route to be // entity.taxonomy_vocabulary.edit_form like it is for other configuration // entities. Taxonomy uses the overview_form as the base route. $local_tasks[$local_task_key]['base_route'] = 'entity.taxonomy_vocabulary.overview_form'; } } /** * Implements hook_entity_operation(). */ #[Hook('entity_operation')] public function entityOperation(EntityInterface $term): array { $operations = []; if ($term instanceof Term && $term->access('create')) { $operations['add-child'] = [ 'title' => $this->t('Add child'), 'weight' => 10, 'url' => Url::fromRoute('entity.taxonomy_term.add_form', [ 'taxonomy_vocabulary' => $term->bundle(), ], [ 'query' => [ 'parent' => $term->id(), ], ]), ]; } return $operations; } /** * @defgroup taxonomy_index Taxonomy indexing * @{ * Functions to maintain taxonomy indexing. * * Taxonomy uses default field storage to store canonical relationships * between terms and fieldable entities. However its most common use case * requires listing all content associated with a term or group of terms * sorted by creation date. To avoid slow queries due to joining across * multiple node and field tables with various conditions and order by * criteria, we maintain a denormalized table with all relationships between * terms, published nodes and common sort criteria such as status, sticky and * created. When using other field storage engines or alternative methods of * denormalizing this data you should set the * taxonomy.settings:maintain_index_table to '0' to avoid unnecessary writes * in SQL. */ /** * Implements hook_ENTITY_TYPE_insert() for node entities. */ #[Hook('node_insert')] public function nodeInsert(EntityInterface $node): void { // Add taxonomy index entries for the node. taxonomy_build_node_index($node); } /** * Implements hook_ENTITY_TYPE_update() for node entities. */ #[Hook('node_update')] public function nodeUpdate(EntityInterface $node): void { // If we're not dealing with the default revision of the node, do not make // any change to the taxonomy index. if (!$node->isDefaultRevision()) { return; } taxonomy_delete_node_index($node); taxonomy_build_node_index($node); } /** * Implements hook_ENTITY_TYPE_predelete() for node entities. */ #[Hook('node_predelete')] public function nodePredelete(EntityInterface $node): void { // Clean up the {taxonomy_index} table when nodes are deleted. taxonomy_delete_node_index($node); } /** * Implements hook_ENTITY_TYPE_delete() for taxonomy_term entities. */ #[Hook('taxonomy_term_delete')] public function taxonomyTermDelete(Term $term): void { if (\Drupal::config('taxonomy.settings')->get('maintain_index_table')) { // Clean up the {taxonomy_index} table when terms are deleted. \Drupal::database()->delete('taxonomy_index')->condition('tid', $term->id())->execute(); } } // phpcs:ignore Drupal.Commenting.InlineComment.DocBlock /** * @} End of "defgroup taxonomy_index". */ }