Project

General

Profile

Actions

Bug #73604

closed

Story #69617: FormEngine bugs

Nested localizations in page module get wrong language pointers

Added by Oliver Hader about 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Localization
Target version:
Start date:
2016-02-22
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
5.5
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Scenario:
  • two additional languages
    • 0/default (english)
    • 1 (german)
    • 2 (french)
  • content element
    • image reference as nested element
  • alternative page localizations (pages_language_overlay) are available already
Test A:
  • for language "german" (uid 1)
  • "translate" button in the page-module
  • use "localization" mode
  • chose "default" as base
  • all fine in sys_file_reference of new localization
    • sys_language_uid points to german (uid 1)
    • l10n_parent points to sys_file_reference of default language
Test B:
  • for language "french" (uid 2)
  • "translate" button in the page-module
  • use "localization" mode
  • chose "german" as base
  • wrong pointers in sys_file_reference of new localization
    • sys_language_uid points to german (uid 1) instead of french (uid 1)
    • l10n_parent points to sys_file_reference of default language instead of german

Files

sys_file_reference.png (25.3 KB) sys_file_reference.png Tymoteusz Motylewski, 2016-11-25 15:14

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #78059: Checks in DataHandler localize mismatch with new Localization WizardClosedDaniel Maier2016-09-25

Actions
Actions

Also available in: Atom PDF