Bug #61179
closedEpic #58282: Workspaces Workpackage #2
Story #58284: Bug fixes & Behaviour
Flaws in copying a page with localized content elements
100%
Description
- in Live Workspace
- Page
- content element for default language
- content element localization with reference to the default record
- in Draft Workspace
- copy the mentioned page
- copy process works
- open new inserted page on Web>List module
- translation for the content element is not shown
- the translation pointer value for the new placeholder is not updated and still points to the record of the origin page
Files
Updated by Gerrit Code Review about 10 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/32356
Updated by Gerrit Code Review over 9 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/32356
Updated by Gerrit Code Review over 9 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/32356
Updated by Daniel Goerz over 9 years ago
- File source-page-from-live-ws.png source-page-from-live-ws.png added
- File copy-of-page-in-ws.png copy-of-page-in-ws.png added
Here is what I do:
In Live WS:- Create a new Page
- Create a translation of that page
- Create a Content Element on that page
- Create a translation of that Content Element
(See Screenshot "source-page-from-live-ws")
- Copy that page
- Insert after that page
- View the new pasted page in page module
(see Screenshot "copy-of-page-in-ws")
- The tranlated Content Element was created twice
- The Button for translate default content is shown nevertheless
- Only one tranlated Content Element
- No "translate default" button
Updated by Oliver Hader about 9 years ago
Thanks for your analysis and documentation of your findings.
Unfortunately, I could not reproduce the duplication issue of the content records - the database view on tt_content seems to be fine as well.
The issue with the button is reproducible however, but needs to be solved differently for the viewing component in the page module (it's a misinterpretation of the record data).
mysql> select uid,pid,sys_language_uid,l18n_parent,header,t3ver_oid,t3ver_state,t3ver_wsid from tt_content order by uid DESC limit 16; +-----+-----+------------------+-------------+----------------------------------------------------+-----------+-------------+------------+ | uid | pid | sys_language_uid | l18n_parent | header | t3ver_oid | t3ver_state | t3ver_wsid | +-----+-----+------------------+-------------+----------------------------------------------------+-----------+-------------+------------+ ### second cloning result of page (53) in draft workspace (1) | 291 | -1 | 1 | 288 | [Translate to German:] Content | 290 | -1 | 1 | | 290 | 56 | 1 | 288 | [Translate to German:] Content | 0 | 1 | 1 | | 289 | -1 | 0 | 0 | Content | 288 | -1 | 1 | | 288 | 56 | 0 | 0 | Content | 0 | 1 | 1 | ### first cloning result of page (53) in draft workspace (1) | 287 | -1 | 1 | 284 | [Translate to German:] Content | 286 | -1 | 1 | | 286 | 54 | 1 | 284 | [Translate to German:] Content | 0 | 1 | 1 | | 285 | -1 | 0 | 0 | Content | 284 | -1 | 1 | | 284 | 54 | 0 | 0 | Content | 0 | 1 | 1 | ### content in default and target language (1) in live workspace | 283 | 53 | 1 | 282 | [Translate to German:] Content | 0 | 0 | 0 | | 282 | 53 | 0 | 0 | Content | 0 | 0 | 0 |
Updated by Oliver Hader about 9 years ago
I guess that #68395 might be a relevant candidate for the button thingy...
Updated by Daniel Goerz about 9 years ago
Did you really apply the patch? I get your results without the patch. No matter what, with the patch I get two translated CEs. maybe someone else can test this as well.
Updated by Daniel Goerz about 9 years ago
OK, I did more tests. Created new PageTrees with two or more languages and wasn't able to reproduce the double creation either. however in the first PageTree I cant make the double creation disappear but I wont blame the pacth any longer and remove my -1. I will investigate further and let you know If I find a way to reproduce the double creation issue.
Updated by Oliver Hader about 9 years ago
- Sprint Focus set to Stabilization Sprint
Updated by Benni Mack about 9 years ago
- Target version changed from 7.5 to 7 LTS
Updated by Gerrit Code Review about 9 years ago
Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/43906
Updated by Oliver Hader about 9 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 6b88e9546985d8038f186954f7a925f86e2c7a4b.
Updated by Riccardo De Contardi about 7 years ago
- Status changed from Resolved to Closed