Project

General

Profile

Actions

Bug #82946

closed

Categories get lost when translating content elements created in a draft workspace

Added by Till Kleisli about 7 years ago. Updated 4 months ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2017-11-07
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
8
PHP Version:
7.0
Tags:
workspaces localization
Complexity:
Is Regression:
Sprint Focus:

Description

1. Create a content element in a draft workspace with some categories assigned.

This will result in
  1. 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
  2. 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
  1. 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
  2. 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.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #81585: Update categories are not visible in Web > ListClosed2017-06-15

Actions
Actions

Also available in: Atom PDF