Moving Elements with Translations in workspaces
We have a website with one alternative language, when in a workspace if you move a default language element then the alternative language version of the element appears on the default language page.
I am using TYPO3 4.5 RC2 this should be easily reproducible.
1. Create a page with at least 2 content elements
2. Localise the page
3. From within a workspace move one of the elements up/down the page
4. The element will be moved as expected, but the alternative language version will appear with the default language elements
I would really appreciate it if this could be fixed for 4.5, we make extensive use of workspaces and will not be able to upgrade whilst this bug is unfixed, this must also be an issue for others using workspaces on a multilingual website?
(issue imported from #M17304)
Updated by Tolleiv Nietsch over 10 years ago
Ok - just reviewed it and I can confirm it. But the risk to break sth. right before the release is imho too big. And this bug was also known for a long time and wasn't introduce with 4.5, therefore I'd prefer to propose a solid solution for one of the next patch level releases of 4.5
Updated by Graham Solomon over 10 years ago
I have just tried applying the following patch to my 4.5.2 installation (I assume this is the latest fix):
typo3core_bugfix_4759_trunk_v2.patch [^] (3,500 bytes) 26.01.11 17:43
When moving an element of the default language the localised version no longer appears on the default language page - however the localised version does not follow the default elements position and remains where it was. Not sure if this is intended, it could cause permissions issues I suppose if a BE user has access to the default language only and is inadvertently moving around localisations when reordering default content, some people may want the localisations to stay in their original position - for the websites I manage though it would be great if the sorting of localisations was 'synced' with that of the default language, perhaps this behaviour could be configurable?
The patch has also introduced a new bug, if I move a default language element in any column other than "Normal", for example moving a content up/down in the right column, it moves across to the normal column.
Updated by Thomas almost 10 years ago
This bug – that renders the usage of the WS useless, since this behavior migth lead to fatal errors – is really four years old?
I am afraid, that this is the tip of the iceberg only. We would love to use workspaces, but came to the conclusion that we can't. And being a developer myself and looking at the current data model (tt_content, pages, pages_language_overlay) I doubt this will ever work flawlessly.
Our hopes got out to the workspaces of Phoenix and the data handling of FLOW3!