Issue Bug Under Review

#110312Workspace preview blank for newly translated content element (connected mode)

Ines Willenbrock 07/28/26, 14:59 updated 11/16/26, 22:33

Description

Summary

When a content element is created and then translated for the first time inside a workspace (before either the page translation or the content element has ever been published), the translated content element does not appear in the frontend workspace preview — the page renders blank (no exception, no error, just missing output). The default-language content element previews correctly at every step. Once both records have been published once, all further edits in the workspace preview correctly again, including edits to the translation.

Environment

- TYPO3 version: 13.4.32
- EXT:workspaces, connected translation mode
- Affected table: `tt_content`

Steps to reproduce

1. Create a new page translation for an existing (live) page inside a workspace. Publish just the page translation (no content yet). → First part of the issue: renders correctly live but nothing but the workspace “decoration” in draft preview.
2. In the workspace, add a new content element (CE) to the page in the default language. → Confirmed working: shows up correctly in the draft preview.
3. Still in the same workspace, translate that CE into the new language. → Bug: the page preview is blank in the workspace/draft preview for the translated language.
4. Publish both the default-language CE and its translation. → Both now show up correctly, live and in draft preview.
5. Edit the translated CE again in the workspace. → Preview now works correctly (shows draft change, live unaffected as expected).

Example DB rows at time of failure (step 3 above)

Default-language CE (renders fine):

```
uid=32915, pid=4054, sys_language_uid=0, l18n_parent=0, l10n_source=NULL,
l10n_state=NULL, t3ver_oid=0, t3ver_wsid=5, t3ver_state=1, t3ver_stage=0,
CType=textmedia, header=“TEST Default“
```

Translation (blank in preview):

```
uid=32916, pid=4054, sys_language_uid=2, l18n_parent=32915, l10n_source=32915,
l10n_state=NULL, t3ver_oid=0, t3ver_wsid=5, t3ver_state=1, t3ver_stage=0,
CType=textmedia, header=“TEST NL“
```

Reviews 1

History 23

  1. Oliver Bartsch commented and changed status New Needs Feedback <span data-processor="relativetime" data-value="2026-10-31T09:16:01+00:00" > 10/31/26, 09:16 </span>

    Hey,

    thanks for the detailed report and the DB rows.

    I checked this against Core. The exact state you describe is already covered by a functional test. In it, the page translation is live, a new default-language content element is created in the workspace, and that element is then translated in the same workspace (both are new records, t3ver_state=1, t3ver_oid=0, and the translation’s l18n_parent points to the new default record). The test then requests the translated page in the frontend with the workspace preview context and checks that the translated element is rendered. It passes, and has existed since TYPO3 v12, so it also covers 13.4. So plain Core rendering (fluid_styled_content, styles.content.get) shows the new translation in the preview.

    Your step 1 is a hint: the translated page already shows nothing but the preview decoration before any content exists, but renders fine live. That points to something at page or setup level rather than the content translation itself. To narrow it down, could you please add:

    • the language part of your site configuration for the affected language (fallbackType, fallbacks)
    • how content is rendered on that page (styles.content.get, a DatabaseQueryProcessor/CONTENT with own language settings, EXT:container, headless, …)
    • the exact URL that is opened for the draft preview (from the workspace module or page module), including the language part
    • whether the page translation has a workspace version (an existing workspace record with t3ver_oid pointing to the page translation) at that point
    • whether it still happens with a minimal setup (fluid_styled_content, no extra extensions)

    With that I can turn the existing test into one that matches your setup and fails.

    Thanks, Oli

  2. Ines Willenbrock commented <span data-processor="relativetime" data-value="2026-11-12T19:00:17+00:00" > 11/12/26, 19:00 </span>

    Hi Oli,

    thank you for your time.

    New pages and translation are visible without setting them so. So no hidden Pages or CEs.

    I added a new untranslated page to the project, translated it in Draft and this is the part of the preview URL that I’m comfortable to share:

    https://www.domain.tld.local/typo3/workspace/preview-control?token=4ae837d6ab304b01c36bd6d788b2cd5e47d9f971&id=5323&_language=2

    Preview of Default is fine with normal page decoration (header and footer), preview of the translation is “just workspaces.
    That stays the same after publishing:

    https://www.domain.tld.local/typo3/workspace/preview-control?token=4ae837d6ab304b01c36bd6d788b2cd5e47d9f971&id=5323&_language=2

    Language part of ID 2:

    
        title: 'Dutch - Netherlands'
        enabled: true
        languageId: '2'
        base: 'https://www.domain.nl'
        typo3Language: nl
        locale: nl_NL.UTF-8
        iso-639-1: nl
        navigationTitle: 'Nederlands'
        hreflang: nl-NL
        direction: ''
        fallbackType: free
        fallbacks: ''
        flag: nl
        baseVariants:
          - base: 'https://www.domain.nl.local/'
            condition: 'applicationContext matches "/^Development/"'

    As I type this: is it possible, that the different domain is the problem of this? DE with similar config but domain.tld(.local)/de/ as URL seems fine.

    Thanks for your patience, this might be a false alarm and “normal” preview trouble.

    Best, Ines

  3. Gerrit Code Review pushed patch set 1 for main to change 97700 status Needs Feedback Under Review <span data-processor="relativetime" data-value="2026-11-16T22:33:42+00:00" > 11/16/26, 22:33 </span>