After update the metatag module, an error arise from the taxonomy image_type metatag field

Created on 13 June 2023, about 1 year ago
Updated 20 June 2023, about 1 year ago

Problem/Motivation

I update the module to the newest version and I get an error, when I try to visit the Taxonomy Overview Page from the vocabulary "Image type".

Error:

Drupal\Component\Plugin\Exception\PluginNotFoundException: 
Unable to determine class for field type 'metatag_computed' found in 
the 'core.base_field_override.taxonomy_term.image_type.metatag' 
configuration in Drupal\Core\Field\FieldConfigStorageBase->mapFromStorageRecords()
(line 31 of /var/www/content/feature-sun-4017/web/core/lib/Drupal/Core/Field/FieldConfigStorageBase.php).

I found out, that I have in the configuration file "core.base_field_override.taxonomy_term.image_type.metatag.yml" which seems to cause the problem. There is a field_type: metatag_computed, which seems not to exists.

uuid: 35d60a01-1a43-4156-a489-2be25764d731
langcode: es
status: true
dependencies:
  config:
    - taxonomy.vocabulary.image_type
  module:
    - metatag
id: taxonomy_term.image_type.metatag
field_name: metatag
entity_type: taxonomy_term
bundle: image_type
label: 'Metatags (Hidden field for JSON support)'
description: 'The computed meta tags for the entity.'
required: false
translatable: false
default_value: {  }
default_value_callback: ''
settings: {  }
field_type: metatag_computed

There is an empty ticket - maybe related:
https://www.drupal.org/project/metatag/issues/3366284 πŸ“Œ Expand Metatag v1 fixture to add Metatag field on Taxonomy Term entity Active

In the release notes, there is a hint to this ticket:
https://www.drupal.org/project/metatag/issues/2945817 πŸ“Œ Support JSON API, REST, GraphQL and custom normalizations via new computed field Fixed

How to prevent this error?

πŸ› Bug report
Status

Closed: works as designed

Version

1.25

Component

Code

Created by

πŸ‡©πŸ‡ͺGermany sreher

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @sreher
  • Status changed to Closed: works as designed about 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States DamienMcKenna NH, USA

    This is because your codebase was using either a patch or merge request from #2945817 and it was lost when you updated. You might want to try updating to v2 instead, the plugin was committed a few weeks ago and will be in the 2.0.0 release.

  • πŸ‡©πŸ‡ͺGermany sreher

    You are right. I wasn't aware of that patch.
    The version 2.0.rc2 save my day.
    Thanks a lot.

Production build 0.69.0 2024