Bug #72547
closed
Moving orig tt_content records does not move translated records
0%
Description
Hello,
I the new localize wizward you told the customer following:
"Translating content will create a direct connection between the original language and the language you translate to."
When I move a tt_content record with help of drag&drop in columns-view the translated record will not be move to the same col.
Stefan
Updated by Tobias H. almost 9 years ago
I can confirm. I wonder why we do have Drag&Drop when it is not working with multilanguage websites? I think it is a bug and should be implemented in 7 LTS.
Updated by Tobias H. almost 9 years ago
New findings: The element is moved, but the page module can not display it correctly. So a page reload will show the translated record in the new position. I did not try it with moving to another colpos.
Updated by David Richter almost 9 years ago
- Target version changed from 8.0 to 7.6.3
T3version 7.6.2
Unfortunately I can't confirm the new findings of you, Tobias.
Even clearing the caches and hard-reloading the backend doesn't move the record for me.
What we found out / Behaviour:
If you click "translate" in the translation wizard, instead of "copy" you have no possibility of moving, neither simply adding any new content in the translated language after that.
Additionally the translated record won't be moved when the original record is moved to another column, as Stefan and Tobias said before.
In my opinion it's definitely a serious bug which makes translating and moving after that impossible. The editors always have to delete the records, move it and localize it again.
The only workaround I've found is:- translate the record
- set the column of the translated record manually in the "column" dropdown of the record settings.
PS we've also tried deactivating EXT:gridelements to eliminate this as a possible cause, changed nothing so it seems very likely to be a core bug.
Updated by Markus Sommer over 8 years ago
- Priority changed from Should have to Must have
- TYPO3 Version changed from 8 to 7
Updated by Jo Hasenau over 8 years ago
When using "translate" in the translation wizard, it is by definition that you can NOT move translations separated from their translation parent in the default language.
If you need to do that, you MUST use the other translation concept which is not connecting default language and translated elements.
This has been treated kind of "loosely" in earlier versions of TYPO3 but CMS 7 now clearly distinguishes between these concepts.
If you have a mixed content, you will see a warning messsage, telling you about content inconsistencies.
So basically this ticket will be about moving translations TOGETHER with their default language parents, which is actually working but not directly visible when using D&D.
The pragmatic approach would be to add a reload action to onDrop as it is already proposed for the new copy on drop feature.
The sophisticated approach would be to connect translated children to their respective parents in the language view and have them switch positions accordingly.
Any opinions?
Updated by Jo Hasenau over 8 years ago
- Status changed from New to Needs Feedback
- Assignee set to Jo Hasenau
Updated by David Richter over 8 years ago
Hi Jo,
thanks for your feedback to this issue.
I agree, the two-way concept of the translations is correct in this form.But we do have two obscurities/questions according to your answer:
- when you want to translate all contents mainly, but then want to add one additional content element only for the translated language, this isn't possible. Is there any way to achieve this?
- We can't confirm that the translated records are moved in a "hidden" way when the original content is moved to another column. Even after a reload the translated CE isn't moved in the correct column where the original one was placed. This was tested on three different, both local and remote, server installations.
Is there anything that we can or have to configure?
Updated by Alexander Opitz over 8 years ago
- Status changed from Needs Feedback to New
- Target version changed from 7.6.3 to Candidate for patchlevel
Updated by
Updated by Stefan Froemken almost 7 years ago
I think we can close this issue now, since we have the new translation handling in TYPO3.
Updated by Riccardo De Contardi almost 7 years ago
- Status changed from New to Closed
- Assignee deleted (
Jo Hasenau) - Target version deleted (
Candidate for patchlevel)
@Stefan I close this one for now, as you requested. Feel free to reopen it (or ping me and I'll do) if the issue comes out again or there is still work left to do. Thanks.