Bug #17610
closed
wrong references between translated content in Workspace and its parent
Added by Marcel Silberhorn over 16 years ago.
Updated over 10 years ago.
Description
1. goto your own workspace
2. enter new content and make a translation afterwards (using the dropdown language Selection in edit mode, perhaps you are in 'de', switch to 'en [new]'
3. "Error 1": "Reference" shows "invalid value ({content id})"
4. save translation and publish content
5. stay in your workspace
6. edit and save the new content in source language again
7. "Error 2:" Language selection in edit mode of the source translation shows up again "en [new ]"
-> clicking "new" and saving content results in an doubled translated content Elementfor the translated Language
-> the already translated ContentElement shows a correct reference to his parent and the diff of the changed content
-> saving a "second translation" results in troubles of wrong references and so on...
reproducable on 4.00 to 4.1.2
(issue imported from #M6357)
Files
According to release policy needs to be fixed in 4.1.x and 4.2.
Up !
There is always the same problem after apply the patch of 0014263 on a 4.2.12.
wow...nearly 3 years ago and not solved?!?!
...really, really disappointing for those who use this in productive environment! ;(
I've located the issue to alt_doc.php which totally ignores versioning in lang selector. Rudimentary fix for 4.3.3 uploaded, might not work in all situations, but gives a good idea of how simply this can be fixed in the core.
Could not reproduct this issue in trunk.
Please check if this issue still exists with trunk or 4.4.2, should be fixed since 4.4.1.
I will close this issue if there won't be any feedback soon.
- Category deleted (
Miscellaneous)
- Status changed from Needs Feedback to Closed
- Target version deleted (
0)
- Category set to Workspaces
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
Also available in: Atom
PDF