Project

General

Profile

Actions

Bug #17610

closed

wrong references between translated content in Workspace and its parent

Added by Marcel Silberhorn about 17 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Category:
Workspaces
Target version:
-
Start date:
2007-09-17
Due date:
% Done:

0%

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

Description

1. goto your own workspace
2. enter new content and make a translation afterwards (using the dropdown language Selection in edit mode, perhaps you are in 'de', switch to 'en [new]'
3. "Error 1": "Reference" shows "invalid value ({content id})"
4. save translation and publish content
5. stay in your workspace
6. edit and save the new content in source language again
7. "Error 2:" Language selection in edit mode of the source translation shows up again "en [new ]"

-> clicking "new" and saving content results in an doubled translated content Elementfor the translated Language

-> the already translated ContentElement shows a correct reference to his parent and the diff of the changed content

-> saving a "second translation" results in troubles of wrong references and so on...

reproducable on 4.00 to 4.1.2
(issue imported from #M6357)


Files

alt_doc.php_r7-r8.diff (1.76 KB) alt_doc.php_r7-r8.diff Administrator Admin, 2010-06-14 13:33
6357.patch (2.34 KB) 6357.patch Administrator Admin, 2010-09-17 23:02

Related issues 4 (0 open4 closed)

Related to TYPO3 Core - Bug #20173: in Draft workspace: changed tt_content-element looses relation to translated element in edit viewClosedBenni Mack2009-03-12

Actions
Related to TYPO3 Core - Bug #22555: Can't translate draft version of element in custom draft workspaceClosedBenni Mack2010-04-30

Actions
Related to TYPO3 Core - Bug #20342: Broken i18n_parent relation upon localizing records in workspaceClosedSteffen Kamper2009-04-22

Actions
Related to TYPO3 Core - Bug #20743: Localization in Workspaces failedClosedBenni Mack2010-08-10

Actions
Actions #1

Updated by Dmitry Dulepov almost 17 years ago

According to release policy needs to be fixed in 4.1.x and 4.2.

Actions #2

Updated by Chris topher over 14 years ago

Related to #0014263.

Actions #3

Updated by Tempestini Cédric [Archriss] over 14 years ago

Up !
There is always the same problem after apply the patch of 0014263 on a 4.2.12.

Actions #4

Updated by Marcel Silberhorn over 14 years ago

wow...nearly 3 years ago and not solved?!?!
...really, really disappointing for those who use this in productive environment! ;(

Actions #5

Updated by Administrator Admin over 14 years ago

I've located the issue to alt_doc.php which totally ignores versioning in lang selector. Rudimentary fix for 4.3.3 uploaded, might not work in all situations, but gives a good idea of how simply this can be fixed in the core.

Actions #6

Updated by Benni Mack about 14 years ago

Could not reproduct this issue in trunk.

Please check if this issue still exists with trunk or 4.4.2, should be fixed since 4.4.1.
I will close this issue if there won't be any feedback soon.

Actions #7

Updated by Benni Mack over 13 years ago

  • Category deleted (Miscellaneous)
  • Status changed from Needs Feedback to Closed
  • Target version deleted (0)

Closed, no response.

Actions #8

Updated by Michael Stucki almost 11 years ago

  • Category set to Workspaces
Actions #9

Updated by Michael Stucki almost 11 years ago

  • Project changed from 624 to TYPO3 Core
  • Category changed from Workspaces to Workspaces
Actions

Also available in: Atom PDF