Bug #78640
closed
Localization fails with nested elements
0%
Description
Since 7.6.11 (and probably also with 7.6.10) you can no longer nest elements properly in a multilanguage setup.
Steps to reproduce:- 1. Create an Element that can contain other Elements and set it to default language NOT 'ALL Languages'.
- 2. Now add as many items in the default language as you want. But when you try to translate an element while editing it with the dropdown-menu above. The translation breaks.
I do get a translated element BUT it's not connected to the original element. The field language shows that the value is invalid. Nor is the select field available from which you could choose the origin element. So you cannot logically reconnect an element origin with its second language element.
This doesn't affect existing nested elements. It only happens when you create a new translation for an element.
This happens in several installations.
Files
Updated by Tymoteusz Motylewski about 8 years ago
- Category set to Localization
- Status changed from New to Needs Feedback
Hi Ralle,
Thanks for your report.
What do you mean by "Element"? is it tt_content?
I need more information to be able to reproduce the issue.
Since 7.6.11 (and probably also with 7.6.10) you can no longer nest elements properly in a multilanguage setup.
In which version it worked?
Can you provide some screenshots?
Updated by Ralle Büchnitz about 8 years ago
- File 01-localization-error.png 01-localization-error.png added
- File 02-localization-error.png 02-localization-error.png added
- File 03-localization-error.png 03-localization-error.png added
- File 04-localization-error.png 04-localization-error.png added
Yes I mean tt_content elements.
I can't tell you a more exact date or version but as you can see in the screens attached it worked before as the customer could create translations for the content elements with translations.
The customer informed me about issues with the localization sometime last month. But he doesn't work on the content each day.
I attached some screenshots from 01-04 to show you how I can reproduce the error.
Updated by Riccardo De Contardi over 7 years ago
- File test1.png test1.png added
- File test2.png test2.png added
- File test3.png test3.png added
- File test4.png test4.png added
- File test5.png test5.png added
- File test6.png test6.png added
- Status changed from Needs Feedback to Closed
I close this issue,as it has been solved in current 7 branch of gridelements - see https://forge.typo3.org/issues/77173;
My test has been performed with TYPO3 7.6.16 and gridelements 7.0.5 (latest from TER):
1) create a page in default language (ITA) and tranlate it in language 1 (ENG)
2) create a gridelements CE (in this case a 2-column element) in default language
3) create two elements in default language (see attached test1.png)
4) page > language mode > click on "Translate" to translate everything (I choosed the "Translate Mode") - the result is test2.png
5) add a content element inside the gridelement in default language (test3.png)
6) if you try to translate it by editing the element and chossing the (new) language in the dropdown, the result can be seen in test4.png
I repeat the point 6 AFTER UPDATING Gridelements to 7.0.6-dev (7 branch on github):
Now the element is translated correctly (test5.png)
Please note that you can always use the button "synchronize with original language" in the gridelement content (test6.png)
which works also on 7.0.5
If you think that this is not the correct decision or experience the issue again or that a different test should be performed, then please reopen the issue or open a different issue with a reference to this one. Thank you.