Project

General

Profile

Actions

Bug #51573

closed

Issues with translations in different workspaces

Added by Michael no-lastname-given over 10 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2013-08-30
Due date:
% Done:

0%

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

Description

Environment:
TYPO3 4.7.12
Workspaces Management 4.7.7
2 workspaces - live (workspace-id 0) and staging (workspace-id 1)
2 languages - default and one more (language-id 1)
Tested as admin

Consider following workflow:

1. Create a new text element in live workspace (workspace-id 0) in default language (language-id 0)
2. Switch to staging workspace (workspace-id 1)
3. Create translation for language-id 1
4. Switch to live workspace (workspace-id 0)
5. Try to create a new translation for the language-id 1 in live workspace (click on "Localize to...")

After the 5th step following happens:
- form opens with all fields pre-filled with data from staging's translation
- if you submit the form, the translation is created in live workspace, but contains standard text instead of the text from the staging (i.e. for the header it's currently "[Translate to .....:] original default header live")
- if you edit the translation again and change the header, translation is saved, but the translation in the staging workspace is overwritten with the translation from live workspace

Expected behaviour:
Both translation are handled separately and only if I push the translation from staging to live, the live translation is overwritten by the staging.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #81691: Issues with translations in workspacesClosed2017-06-23

Actions
Actions

Also available in: Atom PDF