Bug #84682
open
TYPO3 8 Relationship Localization Bug
0%
Description
!When it comes to bidirectional relationships, the localization handling of TYPO3 8 is a bit different than I expected to be.
Let's say, we use price tables and seasons which are connected through a "has many relationship".
I then create a new season and assign them to a price table.
Whenever I translate this season, its connections will also be translated because a new record will be inserted in the mm table.
If I then edit the assigned price table, the season appears twice ( original + language record ).
Additionaly, the sorting attribute of the mm table is broken because the language record receives the default value of sorting ( 0 ).
I've created a minimalistic extension to demonstrate this behaviour.
[[https://github.com/sir-script/mm_typo3_8]]
Can anybody explain,what's wrong here?
What would you expect as standard behaviour?
Should the mm table contain these language overlay records and the presentation is wrong?
Files
Updated by Michael Stucki over 6 years ago
- Project changed from 9 to TYPO3 Core
- TYPO3 Version set to 8
Wrong project.
Updated by Michael Rainer over 6 years ago
Sorry Michael Stucki.
Thanks for moving the project. :)
Updated by Michael Rainer over 6 years ago
- Target version set to 8.7.13
- PHP Version set to 7.0
- Tags set to 8.7.9 LTS
Updated by Michael Rainer over 6 years ago
- Related to Bug #82558: The relation of MM table records are saved wrong for element translations in TYPO3 8.7. added
Updated by Benni Mack over 6 years ago
- Target version changed from 8.7.13 to 8.7.19
Updated by Susanne Moog about 6 years ago
- Target version changed from 8.7.19 to Candidate for patchlevel
Updated by Frank Krüger over 5 years ago
- TYPO3 Version changed from 8 to 9
- Tags changed from 8.7.9 LTS to 9.5.8 LTS
It seems that this is still an issue in TYPO3 9.x
Updated by Wolfgang Klinger about 5 years ago
Still an issue with TYPO3 9, nobody can explain how it should work?
Updated by Jan Kornblum over 4 years ago
I would also like to know what should be the standard behaviour for relations in overlay records currently (9, 10). In my case it seems that an overlays n:1 relation to a parent must point to the parents overlay - instead of the parent default (like it was possible in 8).
Updated by Michael Rainer over 3 years ago
Is there any news on this subject? Anything planned for the next releases?
In our company, we made a quick workaround introducing a new TCA setting,
who prohibits the creation of the mm entries for the language overlays.
But it's not a long term solution and honestly not the right way to do it ;).
Updated by Christian Kuhn over 3 years ago
I hope to work on mm relation stuff, soon. My target will be mostly workspace related, but we'll see what we stumble upon when doing this.
Updated by Michael Rainer over 3 years ago
Christian Kuhn wrote in #note-13:
I hope to work on mm relation stuff, soon. My target will be mostly workspace related, but we'll see what we stumble upon when doing this.
Sounds good. Thank you Christian for the quick response. Wish you good success and hopefully you also come up with a good solution for this issue ( I know, "language handling" and "workspaces" are very complex topics and there are big challenges... ).
Updated by Jan Kornblum over 3 years ago
- Related to Bug #90430: Language handling of bidirectional mm selects is not consitent. added
Updated by Jan Kornblum over 3 years ago
Please could you also have a look at my comment here: https://forge.typo3.org/issues/90430#note-7. To me this seems that the handling of relations at all seem to be a major problem in general in current TYPO3 versions.
Updated by 
