Bug #85337
closed
Translate single content elements after initial translation not working
0%
Description
I have a really strange behavior right now on a page with a lot of languages.
I create a page and its content (english). After that I translate this content to e.g. german with the translation wizard in mode "translate". Everything works fine until here.
If I now add some more content in the english column I would like to translate these additional added contents also, so I press "tarnslate" to open the translate wizard again – now it should provide only the not translated UIDs of content elements from english but it list the UIDs of all the already translated german contents instead of the not translated english contents.
When I ignore this and translate I got the whole german content again (duplicates) in my german row – so it do what it says and "translate"/copy the german content again.
I am using TYPO3 7.6.29.
Updated by Kevin Lieser over 6 years ago
Is nobody interested in fixing this major issue?
Updated by Riccardo De Contardi about 6 years ago
- Status changed from New to Needs Feedback
I cannot reproduce it on 7.6.31, 8.7.19 and 9.5.0
These are the steps I followed:
Prerequisites¶
TYPO3 installation with two languages, italian (Default) and english (uid=1)
procedure¶
1) create a page (Test) in italian and translate it
2) Go to page > languages view
3) Create 2 content elements on the main column of the "Test" page (in italian), call them "test1" and "test2"
4) Translate them ("Translate" mode)
4.1) result: the two elements are present in the english page (correct)
5) Italian > create another two elements ("test3" and "test4")
6) click again on translate
Results¶
1) On all three TYPO3 versions, the wizard only shows "translate" mode (correct)
2) only "test3" and "test4" are listed for the translation
3) after finishing the wizard, the english page contains the translation of the four elements, and no "weird" duplicates
Am I forgetting or misinterpreting something? Could you add a step-by-step guide? Thank you!
Updated by Kevin Lieser about 6 years ago
I have tested a fresh installation and also cannot reproduce it.
Then I copied the project where the problem occurs and I am still unable to reproduce it on new created pages but I am able to reproduce it on these "bug pages".
When I copy these pages the bug is still present in the copy. So this bug only seems to occur on these "buggy pages" in this project.
Updated by Riccardo De Contardi almost 6 years ago
Maybe the "buggy" pages came from an upgrade from an older version? I'm just wild guessing...
Updated by Riccardo De Contardi over 5 years ago
- Status changed from Needs Feedback to Closed
No feedback since the last 90 days => closing this issue.
If you think that this is the wrong decision or experience the issue again and have more information about how to reproduce your problem, please reopen it or ping me.
Thank you and best regards