Issue Bug Closed

#20342Broken i18n_parent relation upon localizing records in workspace

Frank Boegner 04/22/09, 14:53 updated 12/10/13, 01:14

Description

01
As a be user switch to a custom workspace.

02
Then create a new tt_content record on a page.

03
Then save this record and create a localized version of the record by using the “Language” Dropdown on top of the page.

04
Then the i18n_parent Dropdown shows a broken relation.

05
As a result of 04, the localized record is not visible in the frontend.

I traced the error down to alt_doc.php -> languageSwitch. Starting from lines 1074, the $rowsByLang is built. Upon populating this array, the parent’s uid has to be fetched for later use in i18n_parent. Problem is, that currently the workspace “first draft version” is used instead.
(issue imported from #M10958)

Reviews 0

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