A missing field should not cause an exception when trying to save a translation

Created on 23 March 2018, about 6 years ago
Updated 9 March 2022, over 2 years ago

\Drupal\tmgmt_content\Plugin\tmgmt\Source\ContentEntitySource::doSaveTranslations() throws an exception when there is data for a field tha doesn't exist (anymore).

There are valid reasons how that could happen, for example because a field was deleted, or it could have been renamed, like the block_content.content_translation_status field during the 8.5.0 update.

🐛 Bug report
Status

Needs work

Version

1.0

Component

Source: Entity

Created by

🇨🇭Switzerland Berdir Switzerland

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024