Actions
Bug #89448
openEpic #90050: Translation wizard improvements and issues
Translation Wizard can get stuck
Status:
New
Priority:
Should have
Assignee:
-
Category:
Localization
Target version:
-
Start date:
2019-10-18
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
The translation wizard can get stuck when no elements are available for translation from a given language.
Steps to reproduce- Have at least two languages besides "default" (language 1 and language 2)
- Create an new page and translate to both languages
- Create content element1 in default.
- Translate element1 to language 1 with translation wizard
- Translate element1 to language 2 with translation wizard but chose language 1 as source
- Create content element2 in default.
- Translate element2 to language 2 with translation wizard
As element1 was translated from language 1 and element2 does not exist in language 1 yet, the translation wizard tries to translate element2 fro language 1 again, cant submit any elements and therefore triggers a bad request (400) response which causes the wizard to die, blocking the UI without any option to close it again.
Updated by Frank Nägler about 5 years ago
- Category changed from Backend User Interface to Localization
Updated by Riccardo De Contardi over 4 years ago
The issue is still reproducible on 11.0.0-dev with the steps in the description above (I used "translate" mode).
Updated by Riccardo De Contardi over 1 year ago
The issue is still reproducible on 13.0.0-dev with the steps in the description above (I used "translate" mode).
Updated by Riccardo De Contardi over 1 year ago
- Related to Bug #90051: User get stuck when translation wizard fails added
Updated by Jo Hasenau over 1 year ago
- Related to Story #101564: User Interface related translation issues added
Actions