Issue Bug Under Review

#111489Workspace preview of translated page fails with Unknown column '_TRANSLATION_SOURCE'

Himanshu Ramavat 11/18/26, 12:03 updated 11/18/26, 12:05

Description

When previewing a non-default language page while a workspace is selected
(e.g. Staging + English), the frontend returns a 503:

An exception occurred while executing a query:
Unknown column ‘_TRANSLATION_SOURCE’ in ‘field list’

*How to reproduce*
1. Enable workspaces and create a Staging workspace.
2. Have a page with a connected-mode translation (e.g. German default,
English translation).
3. In the backend, select the Staging workspace.
4. Open the page module, select the translated language, and use
“View” / frontend preview.

Expected: translated page renders in workspace preview.
Actual: 503 with Unknown column ‘_TRANSLATION_SOURCE’.

*Root cause*
PageRepository::getPageOverlay() attaches the virtual property
_TRANSLATION_SOURCE (a Page object) to the page row.

versionOL() / getWorkspaceVersionOfRecord() then build the SQL SELECT
list from array_keys(purgeComputedProperties($row)).
_TRANSLATION_SOURCE was missing from COMPUTED_PROPERTY_NAMES, so it
leaked into the field list and MariaDB/MySQL rejected the query.

Note: SQLite may not always fail the same way; MariaDB/MySQL do.

*Suggested fix*
Add ‘_TRANSLATION_SOURCE’ to PageRepository::COMPUTED_PROPERTY_NAMES
so it is stripped before workspace overlay queries, same as
_LOCALIZED_UID / _ORIG_uid / etc.

This is unrelated to #108496 / https://review.typo3.org/c/Packages/TYPO3.CMS/+/92672
(which only handles _TRANSLATION_SOURCE in MenuProcessor JSON encoding).

Reviews 1

History 01