Project

General

Profile

Actions

Bug #79755

closed

allowLanguageSynchronization triggers exception in translation page modal

Added by Christian Kuhn almost 8 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
Start date:
2017-02-11
Due date:
% Done:

100%

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

Description

Enable synchronization for header field in tt_content:

typo3/sysext/frontend/Configuration/TCA/tt_content.php:

'header' => [
   ...
   'behaviour' => [
      'allowLanguageSynchronization' => true,
   ],
],
  • Create a page
  • Create two page localizations
  • Add default content element 'Regular text element' or similar in default language
  • Use page module Language view
  • Translate content element to first locaziled page:
    "translate button" in column -> modal -> translate -> default
    The first translation is created successfully
  • Translate content element of second localized page, but select first localized page as translation source!
    "translate button" in column -> modal -> translate -> first localizaton (german for me) -> do -> modal does not close.

Inspecting network of last modal shows a fatal:

Uncaught TYPO3 Exception
Argument 1 passed to TYPO3\CMS\Core\DataHandling\Localization\State::update() must be of the type array, string given, called in typo3/sysext/core/Classes/DataHandling/Localization/DataMapItem.php on line 320

This only happens if a content element has a different l10n_source that default lang in the modal.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #79658: Introduce allowLanguageSynchronizationClosed2017-02-07

Actions
Related to TYPO3 Core - Bug #88974: Wrong l10n_state after copying a recordClosed2019-08-19

Actions
Actions

Also available in: Atom PDF