When having a content type or a media bundle. When you click enable translation of the entity the columns ( content_translation_source, content_translation_outdated, content_translation_uid ) are being added. But when disabling the translation for that entity I would think they should be removed but they still remain.

Then a side note. I ran across this issue because I have a missing column after a config import. So it would be great if there could be a check if the translation is enabled en one of the columns is missing. The columns will be added again.

Columns for media are being added on table media_field_data and media_field_revision
Columns for node are being added on table node_field_data and node_field_revision

Comments

ruudvanoijen created an issue. See original summary.

ruudvanoijen’s picture

ruudvanoijen commented
Related issues: +#2419649: Content translation schema updates are not triggered consistently, +#2418563: Column not found: 1054 Unknown column 'content_translation_source', +#2346013: Improve DX of manually applying entity/field storage definition updates
ruudvanoijen’s picture

ruudvanoijen commented
Issue summary: View changes

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

sealionking’s picture

sealionking commented

when I enable translation for a vocabulary terms, the status report says entity taxonomy terms need to update for

content_translation_source, content_translation_outdated, content_translation_uid ,

Mismatched entity and/or field definitions
The following changes were detected in the entity type and field definitions.
Taxonomy term
The Translation source field needs to be updated.
The Translation outdated field needs to be updated.
The Translation author field needs to be updated.
The Translation created time field needs to be updated.

but after executed the command with drupalconsole

drupal upe

I got the alert that:

[ERROR] Drupal\Core\Entity\EntityStorageException: Exception thrown while performing a schema update. SQLSTATE[42S22]:
Column not found: 1054 Unknown column 'content_translation_source' in 'where clause': SELECT 1 AS expression
FROM
{taxonomy_term_field_data} t
WHERE content_translation_source IS NOT NULL
LIMIT 1 OFFSET 0; Array
(
)
in Drupal\Core\Entity\Sql\SqlContentEntityStorage->wrapSchemaException() (line 1481 of
/docroot/web/core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php).

I think this is the same problem.

my drupal version is 8.6.3

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone commented
Status: Active » Closed (works as designed)
Issue tags: +Bug Smash Initiative

I got this issue from the bugsmash bug bingo.

I do think this is working as designed. Removing those database columns could interfere with translations for other content types. And there is always the possibility of loss of data.

I am closing this as works as designed. If you disagree, re-open (by setting status to 'Active') and explain what I missed.

Thanks