Project

General

Profile

Actions

Bug #98256

open

l10n_mode: exclude not properly working in workspaces

Added by Armin Vieweg over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
DataHandler aka TCEmain
Target version:
-
Start date:
2022-09-04
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
11
PHP Version:
8.1
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

When you are in e.g. in a draft workspace and you change a property of a record which has l10n_mode set to exclude, TYPO3 does not set the value of the translations, properly. Those values remain untouched. You can test it with the "layout" field of pages.

When updating in LIVE workspace, all translation get the new layout value set.
When in e.g. draft workspace, only the default language record gets changed.

When publishing to LIVE, those wrong values remain in place. You need to update the value in LIVE workspace, to get proper results.


Related issues 1 (1 open0 closed)

Related to TYPO3 Core - Task #80640: Enhance workspace handling of language synchronizationUnder ReviewOliver Hader2017-04-02

Actions
Actions #1

Updated by Oliver Hader over 1 year ago

  • Related to Task #80640: Enhance workspace handling of language synchronization added
Actions #2

Updated by Armin Vieweg over 1 year ago

I also discovered a related issue with Extbase:

I created an Extbase Repo pointing to pages table. In one findBy... method I added a constraint for the Doktype of page.

- But instead of checking the Doktype of records in current workspace, it uses the value from the published page in LIVE workspace.
- When the page is NOT published to LIVE, it works as expected
- It seems only to affect properties, with l10n_mode: exclude set (like "layout" or "doktype")

Actions

Also available in: Atom PDF