#82946Categories get lost when translating content elements created in a draft workspace
Description
1. Create a content element in a draft workspace with some categories assigned.
This will result in- PLACEHOLDER-Element with uid 42 (for example)
- t3ver_label: INITIAL PLACEHOLDER
- t3ver_oid: 0
- t3ver_wsid: 1 (Workspace-Id)
- t3ver_state: 1
- t3origuid: 0
- sys_language_uid: 0
- No categories assigned
- Draft element with uid 43
- pid: -1
- t3ver_oid: 42
- t3ver_label: First draft version
- t3ver_wsid: 1 (Workspace-Id)
- t3ver_state: -1
- Entries in table sys_category_record_mm are made with uid 43
2. Make a translation of this element
You get- New translated placeholder
- uid: 44
- t3ver_label: INITIAL PLACEHOLDER
- t3ver_oid: 0
- t3ver_wsid: 1
- t3ver_state: 1
- t3origuid: 42
- sys_language_uid: 1
- No categories assigned
- new translated draft
- uid: 45
- pid: -1
- t3ver_oid: 44
- tever_label: First draft version
- t3ver_wsid: 1 (Workspace-Id)
- t3ver_state: -1
- t3origuid: 42
- sys_language_uid: 1
- No categories assigned
3. Problem
The translated elements do not have the categories assigned.
The reason is, the translations are always made from the Placeholder record (uid 42) which has no categories assigned. The categories only get assigned to the placeholder record, when the element is published to the LIVE workspace.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 1
History 7
-
Till Kleisli changed Related to #81585 11/07/17, 21:55
-
Till Kleisli commented 11/07/17, 22:12
-
Susanne Moog changed Sprint Focus On Location Sprint 11/24/17, 22:59
-
Mathias Brodala changed Sprint Focus
On Location Sprint03/09/18, 14:49 -
Riccardo De Contardi commented 08/30/20, 10:57
are these somehow related?
#77917
#82086
#89231
-
Riccardo De Contardi commented and changed status
NewNeeds Feedback 04/20/24, 22:07IS this still true? I tried to reproduce it with 11.5.35, 12.4.14 and 13.1.0-dev (latest main) with the following test
Prerequisites
- TYPO3 installation with two languages (default id=0 e.g. Italian and another id=1 e.g. Englisgh)
- a Draft workspace
- some categories
Test procedure
- on LIVE workspace create a page “test” and translate it to the 2nd language
- switch to “Draft” workspace (important)
- create a content element, e.g “header only” and assign to it some categories; save it and close
- Translate the CE into the 2nd language
- edit it
Result
Both using the “connected” and “free” translation mode, when you edit the 2nd element, the same categories you selected are applied
Do you think that this test is sufficient? Or a different one is necessary?
-
Riccardo De Contardi commented and changed status
Needs FeedbackClosed 07/23/24, 08:06No feedback within 90 days > I close this issue.
If you think that this is the wrong decision or experience the issue again or there is still work to be done here, please reopen it or open a new issue with a reference to this one.
Thank you.
I would provie a patch, when someone can tell me, where I have to look for the code that is creating the localized elements.