Skip to content

Comments

[BUGFIX] Display inline elements in correct language (fixes #19)#24

Open
PBahner wants to merge 2 commits intoteam23:mainfrom
PBahner:19-translation-correction
Open

[BUGFIX] Display inline elements in correct language (fixes #19)#24
PBahner wants to merge 2 commits intoteam23:mainfrom
PBahner:19-translation-correction

Conversation

@PBahner
Copy link

@PBahner PBahner commented Nov 6, 2025

What?

This pull request fixes the issue where translated content elements were incorrectly displayed inline as children of the original language container and appeared untranslated within the translated container.

Additionally, it updates the required version of b13/container to support v3 (includes #20, #21).

Why?

Without this fix, the extension is not suitable for multi-language environments.
Furthermore, b13/container cannot be used as a replacement for extensions like mask or gridelements in setups that rely on inline content elements.

How?

  • Added a custom FormDataProvider that:
    • Filters out content elements from other languages in the original language container.
    • Adjusts isInlineDefaultLanguageRecordInLocalizedParentContext so that translated elements are editable within their translated container.
  • Modified the DataProcessor to always store the original language parent container in the database for translated inline elements, aligning with the behavior of b13/container.

Version

I have bumped the version to 0.0.14.

timo.klinge added 2 commits November 6, 2025 11:02
- hide translated inline elements in original language
- show inline elements in correct language
- fixes team23#19
@PBahner
Copy link
Author

PBahner commented Nov 6, 2025

this change is part of #25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant