Bug #59734

Translating a CE containing inline elements doesn't apply language to inline elements

Added by Teamgeist Medien almost 5 years ago. Updated 7 months ago.

Status:
New
Priority:
Must have
Assignee:
-
Category:
FormEngine aka TCEforms
Target version:
-
Start date:
2014-06-20
Due date:
% Done:

0%

TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Well this could be an OSI8 (user mistakes) but I've tried every possible combination of the flexform behavior configuration.
When I have a Content Element with a custom inline element configured by flexform and create some inline elements everything is fine. But when i choose to translate all contents to another language (localization) the inline elements are always active in the default language and every change will also be applied on default language elements.

Maybe the options localizationMode or localizeChildrenAtParentLocalization doesn't work?

Heres an example flexform field configuration which won't work fine with localization:

<config>
    <type>inline</type>
    <foreign_table>tx_tgmirrelinks_domain_model_link</foreign_table>
    <minitems>0</minitems>
    <maxitems>99</maxitems>
    <foreign_sortby>sorting</foreign_sortby>
    <foreign_match_fields>
        <fieldname>themenLinks</fieldname>
    </foreign_match_fields>

    <appearance>
        <useSortable>1</useSortable>

        <showPossibleLocalizationRecords>1</showPossibleLocalizationRecords>
        <showRemovedLocalizationRecords>1</showRemovedLocalizationRecords>
        <showSynchronizationLink>1</showSynchronizationLink>

        <createNewRelationLinkTitle>LLL:EXT:cms/locallang_ttc.xlf:images.addFileReference</createNewRelationLinkTitle>
    </appearance>

    <behaviour>
        <localizationMode>select</localizationMode>
        <localizeChildrenAtParentLocalization>0</localizeChildrenAtParentLocalization>
    </behaviour>
</config>
Step by Step:
  • Create a flexform with an inline element
  • Create some inline elements and save the CE in the default language
  • Go to the localization view of the "Page" view and choose "Copy default content elements / Standardinhalte kopieren"
  • Open the translated CE and watch the inline records of the default language are activated

Related issues

Related to TYPO3 Core - Bug #56882: Can not translate IRRE elements Closed 2014-03-13
Related to TYPO3 Core - Bug #63092: Inline/IRRE records: language field of child records is not updated when modifying parent language field - e.g. problematic for sys_file_reference Rejected 2014-11-20
Related to TYPO3 Core - Bug #48883: Wrong sys_language_uid in sys_file_reference Closed 2013-06-05
Related to TYPO3 Core - Bug #62562: Flexforms - Translating with inline relations doesn't work Rejected 2014-10-30

History

#1 Updated by Tymoteusz Motylewski almost 5 years ago

isn't it a duplicate of #56882 ?

#2 Updated by Mathias Schreiber over 4 years ago

  • Status changed from New to Needs Feedback
  • Assignee set to Mathias Schreiber

Hey guys,

can you check if this is still the case?

#3 Updated by Fabian Schöner about 4 years ago

Hey Mathias,

i just hit the exact same issue as described here.

TYPO3 6.2.12.
Once you translate a CE with Flexform Inline Relations the records are "copied" in DB, but neither sys_language_uid nor l18n_parent are properly set.
It would work if those fields would be properly set (done that manually in database to test it).

#4 Updated by Alexander Opitz almost 4 years ago

  • Status changed from Needs Feedback to New
  • Assignee deleted (Mathias Schreiber)

#5 Updated by Mathias Schreiber over 3 years ago

  • Target version deleted (next-patchlevel)

#6 Updated by Markus Mächler Mächler almost 2 years ago

This is still an issue in TYPO3 7.6. I think this is related to issue https://forge.typo3.org/issues/62562.

#7 Updated by Markus Mächler Mächler almost 2 years ago

  • Related to Bug #62562: Flexforms - Translating with inline relations doesn't work added

#8 Updated by Loon Buster 10 months ago

  • TYPO3 Version changed from 6.2 to 8

..any news after 4 years? that's so disappointed. sad, really sad.

#9 Updated by Ingo Fabbri 7 months ago

yep - nobody cares about flexform.

Also available in: Atom PDF