Project

General

Profile

Actions

Bug #20342

closed

Broken i18n_parent relation upon localizing records in workspace

Added by Frank Boegner about 15 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Category:
Workspaces
Target version:
-
Start date:
2009-04-22
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.2
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

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)


Files

screen.jpg (213 KB) screen.jpg Administrator Admin, 2009-04-22 14:53
10958.patch (598 Bytes) 10958.patch Administrator Admin, 2010-04-10 10:04
10958v2.patch (1.21 KB) 10958v2.patch Administrator Admin, 2010-04-10 10:32

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #17610: wrong references between translated content in Workspace and its parentClosedBenni Mack2007-09-17

Actions
Actions #1

Updated by Steffen Kamper almost 14 years ago

Committed to trunk rev 8094 and 4_4 rev 8095

Actions #2

Updated by Michael Stucki over 10 years ago

  • Category set to Workspaces
Actions #3

Updated by Michael Stucki over 10 years ago

  • Project changed from 624 to TYPO3 Core
  • Category changed from Workspaces to Workspaces
  • Target version deleted (0)
Actions

Also available in: Atom PDF