Project

General

Profile

Actions

Bug #78955

closed

“language” menu on top of the content element is missing the possibility to create [NEW] translations out of every language selection

Added by Patrick Gaiser over 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Localization
Target version:
-
Start date:
2016-12-12
Due date:
% Done:

0%

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

Description

The “language” menu on top of the content element is missing the possibility to create [NEW] translations out of every language selection you have chosen.
Translation is only possible on the default language.

This behavior appears since Typo3 Core 7.6.13.
I guess the fix for Bug #72797 has caused this issue.

Steps to reproduce:

1) have 15 languages (default language is English, ID=0)
2) have a page with 15 languages, go on it, select “languages” view
3) create a new content element in the default language (English)
4) create a translation from this content element in another language, e.g. Chinese
look at localization_1.jpg

5) now if you want to create the German translation, you first have to switch back to the default language before you can choose “Deutsch [NEW]” because there is no such a option available in the language selection.
look at localization_2.jpg

I think this step to switch back to the default language is unnecessary and doesn’t have good affects for editorial work in Typo3 backend because in case of bigger content elements this takes a lot of time to switch each time for every language.

--> until Typo3 Core 7.6.12 you’ve got the possibility to create a translation with the [NEW] language selection from every language (not even from the default language).
For example it was possible to create German translation from Chinese content.
look at localization_3.jpg


Files

localization_1.jpg (24.4 KB) localization_1.jpg Patrick Gaiser, 2016-12-12 09:55
localization_2.jpg (17.2 KB) localization_2.jpg Patrick Gaiser, 2016-12-12 09:55
localization_3.jpg (21.2 KB) localization_3.jpg Patrick Gaiser, 2016-12-12 09:55
Schermata 2017-09-15 alle 21.48.04.png (80.7 KB) Schermata 2017-09-15 alle 21.48.04.png Riccardo De Contardi, 2017-09-15 21:49

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #72797: EditDocumentController / languageSwitch / localized records without a default language record relationClosed2016-01-18

Actions
Actions #1

Updated by Patrick Gaiser over 7 years ago

It looks like there is an solution available shortly with BUG #72797.

Actions #2

Updated by Riccardo De Contardi over 6 years ago

Hello and sorry for the latest answer; Can you try with 8.7.6 or the latest master? I think it has been solved: This is what I tried to do with the latest master:

1) I have a page in 5 languages: Italian (default), English, Czech, French, Danish
2) create a content element in Italian
3) translate it in English
4) edit english record
5) opening the "Languages" dropdown I see all languages (See attached screenshot)

Do you think it is sufficient or a different test should be performed? Thank you.

Actions #3

Updated by Alexander Opitz over 6 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions #4

Updated by Alexander Opitz over 6 years ago

  • Target version deleted (Candidate for patchlevel)
Actions

Also available in: Atom PDF