TYPO3 Core

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")

I tried the following test on TYPO3 13.2.0-dev (latest main)

Prerequisites¶

• TYPO3 with two languages: Italian (Default, ID=0) and English (ID=1)
• a "Draft" Workspace
• A simple TypoScript template like:

page = PAGE
page {
  5 = TEXT
  5 {
      data = field : title
      wrap = <h1>|</h1>
    }

  6 = TEXT
  6.data = field:layout
  6.wrap = <h2>Layout: | </h2>
}

Test procedure¶

1) Create a page "Test" in Italian (default language ID=0)
2) Translate the page in English and rename it "Test ENG"
3) Edit the italian version of the page and set the Frontend Layout [layout] field: "Layout 1"
4) Save and preview the page

Result 1 (preview of the "LIVE" workspace)¶

• the Italian page Test has Layout:1 (OK)
• the English page Test ENG has Layout:1 (OK)

5) Switch to "Draft" workspace
6) Edit the italian version of the page and set the Frontend Layout [layout] field: "Layout 3"
7) Save and preview the page

Result 2 (preview of the "Draft" workspace)¶

• the Italian page Test has Layout:3 (OK)
• the English page Test ENG has Layout:3 (OK)

Is a different test necessary?

The reason seems to be that the workspace-version of the page translation has its parent set to the UID of the live-version of the default language page.

\TYPO3\CMS\Core\DataHandling\Localization\DataMapProcessor::fetchDependentElements

tries to find the translations, but does not find them due to searching for translations pointing to the workspace-version of the default language.

Probably t3_origuid of the workspace-version must be used to search for translated pages in the workspace.

Example:

With this demo-data it would search for dependencies by using uid 3, which will not reveal record uid 4, as it points to parent with uid 1.