Compatibility with dynamic field property translation

Created on 12 June 2025, 15 days ago

Problem/Motivation

I am using the "custom_field" module, for custom fields within Layout Builder blocks.
To get those translated via the AI Translate module, the following patch is needed: ✨ Don't hardcode 'value' key for textual field translation Active .
Once this patch is applied, this works with this module, except for one code check, where the hardcoded 'value' property is checked.

Proposed resolution

Do not rely on the hardcoded 'value' property to be present.

✨ Feature request

Status

Active

Version

1.0

Component

Code

Created by

🇧🇪Belgium svendecabooter Gent

Live updates comments and jobs are added and updated live.

Merge Requests

!2Compatibility with dynamic field property translation
Open
🇧🇪Belgium svendecabooter
updated 15 days ago

Comments & Activities

Issue created by @svendecabooter
Merge request !2Do not check for explicit 'value' key, but just check if the translated data array is not empty → (Open) created by svendecabooter
Pipeline finished with Success
15 days ago
Total: 159s
#520800
Comment 15 days ago →
🇧🇪Belgium svendecabooter Gent
Patch file included for composer-based patching workflows.
Comment 1 day ago →
🇧🇪Belgium svendecabooter Gent
A better fix for this issue is implemented in 📌 Set block entity values via FieldTextExtractor plugins Active

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024

Compatibility with dynamic field property translation

Problem/Motivation

Proposed resolution

Merge Requests

!2Compatibility with dynamic field property translationOpen

Comments & Activities

!2Compatibility with dynamic field property translation
Open