Translated field definition are not available as source field

Created on 3 August 2022, over 2 years ago
Updated 14 June 2024, 8 months ago

Problem/Motivation

If in the source database a field definition is translated (ex. a different label) the ContetntEntity:getFields method will exclude the field because the config query is keyd by name and there are multiple row with different collection.

Steps to reproduce

In the source database create a field and add a translation for the field definition, create a migration with the translated field and verify that the field is not presente in the source record.

Proposed resolution

Alter the query to retrieve only rows with empty collection.

Remaining tasks

Add a translated field definition to the ContentEntityTest.

🐛 Bug report
Status

Fixed

Version

1.0

Component

Code

Created by

🇮🇹Italy vdupom

Live updates comments and jobs are added and updated live.
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.71.5 2024