Content Translation Module Error

Created on 31 May 2024, about 1 year ago

Problem/Motivation

On a multi site setup with multi language configuration, on any subsite with a translation, we have the following error:

Error: Class name must be a valid object or a string in Drupal\content_translation\ContentTranslationManager->getTranslationMetadata() (line 56 of /var/www/html/web/core/modules/content_translation/src/ContentTranslationManager.php).

Steps to reproduce

We cannot identify the cause.

🐛 Bug report
Status

Active

Version

10.1

Component
Content translation 

Last updated 7 days ago

No maintainer
Created by

🇷🇴Romania adrianpintilie

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

Comments & Activities

  • Issue created by @adrianpintilie
  • Status changed to Postponed: needs info about 1 year ago
  • 🇳🇿New Zealand quietone

    I agree that we need to know how to reproduce this before we can work on resolving it.

  • 🇳🇿New Zealand quietone

    While this was reported on 10.1, any fix will be applied to 11.x (main) first.

  • 🇵🇹Portugal introfini

    I occasionally encounter this error on multilingual websites as well. It typically resolves with a cache clear via `drush cr` or by running `drush ev "drupal_flush_all_caches();"`.

  • 🇭🇺Hungary denes.szabo Hungary

    I have a website with domain module and ~5 translations on the site.

    I can reproduce this exception when I make an sql backup with drush (with a bash alias, like: cd ~/website/; vendor/bin/drush cr; vendor/bin/drush sql-dump --gzip >filename.gz).

    Then, I get this error in the php error log when I try to access a translated node on the site.

    To fix it, I have to clear the cache, then the site and the node above are accessible again.

  • 🇻🇳Vietnam nguyenphan Hanoi, Vietnam

    I'd like to provide some additional information:

    I'm using database caching, and later switched to Redis, but the issue still occasionally occurs.I suspect the problem might be related to the use of the Paragraphs module.It seems that the issue occurs when the cache is not loaded properly, which may cause missing configuration or entity cache data.

Production build 0.71.5 2024