LCH-6801: Use default field name for langcode when langcode field is not specified.

Created on 1 February 2024, about 1 year ago

Problem/Motivation

This is a patch based on a patch provided by Acquia support. Since it no longer applies and is still not fixed in the upstream I'm re rolling it here as a MR.

🐛 Bug report

Status

RTBC

Version

3.4

Component

Code

Created by

🇧🇪Belgium BramDriesen Belgium 🇧🇪

Live updates comments and jobs are added and updated live.

Merge Requests

!29LCH-6801: Use default field name for langcode when langcode field is not specified.
Open
🇧🇪Belgium BramDriesen
updated about 1 year ago

Comments & Activities

Issue created by @BramDriesen
Merge request !29feat: Re-applied langcode logic → (Open) created by BramDriesen
Status changed to RTBC about 1 year ago1:11pm 1 February 2024
Comment about 1 year ago →
🇧🇪Belgium BramDriesen Belgium 🇧🇪
Setting to RTBC as this patch was provided by Acquia support, we're using it for a ling time in production, and it resolves an issue for us.
Pipeline finished with Failed
about 1 year ago
Total: 3693s
#86086

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024

LCH-6801: Use default field name for langcode when langcode field is not specified.

Problem/Motivation

Merge Requests

!29LCH-6801: Use default field name for langcode when langcode field is not specified.Open

Comments & Activities

!29LCH-6801: Use default field name for langcode when langcode field is not specified.
Open