Issue Bug Closed

#73604Nested localizations in page module get wrong language pointers

Oliver Hader 02/22/16, 19:05 updated 01/13/17, 16:52

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

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.