fix: create locale column when migrating from v4 #20261
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does it do?
Migrating from v4 content types with i18n disabled resulted in the following error:
The cause was the
locale
column not being in the database for those content types. It is assumed , in v5, that the locale column will be present even if i18n is disabled on a content type.This fix proposes adding a locale column in the discard-draft migration, similarly to how we add the document_id in another migration.