Translated elements are not moved within grid container, when language parent is moved - Regression?
I had exactly the same behaviour for translated elements as has been described in #73055 (so I'm not stating it here all again).
T3-Version is 7.6.10. Is this a regression?
#2 Updated by Jo Hasenau over 2 years ago
- Status changed from New to Needs Feedback
- Assignee changed from Martin R. Krause to Jo Hasenau
Did you test with latest 7-0 branch already?
If yes, how to reproduce the buggy behaviour, since moving elements currently works on our testing environment?
Did you translate the elements using "translate" or using "copy" in the translations modal of the page module?
#3 Updated by Kaan Sanli over 2 years ago
Behaviour was seen on 7.6.10 from typo3.org. Not yet tested with latest 7-0 branch.
It was my first thought, that there is some mismatch in the relations betwen language parent and child after an upgrade from 6.2 to 7.6.10, so I deleted the translated container and its contained elements. After that I translated the whole container with its elements from within the container switching from default language to english [NEW] - so I think this is copy, right?
But the behaviour still is buggy.
#4 Updated by Kaan Sanli over 2 years ago
Tested with latest 7-0 branch, but same problem. Drag & Drop between grid container columns in german (default) is not comprehend in english (L=1), the english items are stucked in the column, where the before moved language parent was positioned. Also the language childs were set to top in the now wrong column, although the sorting in database is still correct.
#5 Updated by Jörg Wagner over 2 years ago
Kaan, are you sure you cleared all caches (maybe uninstall/reinstall GridElements)?
We had that very same problem with 7.0.5 but it was definitely solved by switching to the latest 7-0 snapshot.
What we still experience:
After adding new children to a GridElement in the default language and syncing its language overlays, the child copies in the translations are always added to the very end of the list of children - no matter what the sort order is in the default language.
A workaround for this: Chang the sort order in the default language once (e.g. through drag&drop). When you do that the children in the language overlayes are resorted in sync with the default language.
#6 Updated by Jo Hasenau over 2 years ago
@Jörg The missing sorting after synchronization is a known core bug #68040
@Kaan "Switching from default language to english [NEW]" is not the copy mode and currently broken due to another known core bug #63092
The modes I have been talking about are the ones to choose from when you click on the "Translate" button in the page module.
There is "Translate" which creates connections bewtween translated child and default parent and "Copy" which does just that.
Copy again is currently broken #75400 but with a pending patch, which is close to being merged.
The idea of the different modes is:
In the connected mode, the default language got the lead, so you can not do anything with the translated children but changing their content. No moving, no D&D, just content changes and deleting is possible.
In the free mode, you can do whatever you want with the children, but there is no connection to manage everything from the default language. Thus more freedom but more work too, especially when it comes to a lot of different languages.
There currently is still a hybrid mode, but only when you set the TSconfig switch
mod.web_layout.allowInconsistentLanguageHandling = 1
#7 Updated by Jörg Wagner over 2 years ago
I was not aware of that "hybrid" mode that you mention. Now I looked it up and it looks like something we have actually been looking for. I.e. the possibility to put language specific content inbetween connected/synced language overlay elements.
But you state: "...there STILL is..."
So I ask myself whether this is a way to rely on or whether this is kind of deprecated. Could you just give a quick opinion on that?
THANKS! (as always!)
#8 Updated by Kaan Sanli over 2 years ago
He guys, thanks for your hints and efforts.
Tried to use the latest gridelements snapshot again on a cloned T3-installation and everything works fine, the bug is solved with 7.0.6-dev. Only have to check, why it hasn't worked the first time I used the latest 7-0-branch on the production system.
Little update on that issue with 7.0.5: The change of the gridelements_column for an item is not comprehended by is language child. But if you change the position of an item within the gridelements_column, the language child is moved to the same position.
@Jo: I used the Translate button in page modul and then chose the mode 'Translate' with 7.0.5, but the error still occured.
So how to go on with this ticket? Right now I only have this one installation using T3 7.6, grids and languages, and I assume it will be only a question of time, until 7.0.6 will be released. So for me, the ticket could be closed.
On the other hand, there is a difference in the behaviour for moving the language parents and their childs from one gridelements_column to another between 7.0.5 and 7.0.6, and the problem had been solved for 7.0.4 (as has been stated in [[#73055]]) but occured again using 7.0.5. Is it worth searching for the difference between 7.0.5 and 7.0.6 producing that inconsistent behaviour?