Issue Task Under Review Stale

#109304Add workspace regression coverage for language-all clipboard paste

Eric Harrer 03/20/26, 12:24 updated 08/06/26, 16:02

Description

Summary

The TYPO3 Core already contains a dedicated DataHandler guard for language-all records (sys_language_uid = -1) in the extended paste command path:

if ($row[$languageField] === -1 && (int)$languageId === 0) {
    $value['update'][$languageField] = $row[$languageField];
}

The live clipboard paste scenario is already covered by functional tests. However, the corresponding workspace copy scenarios are still missing.

Context

Relevant runtime path:

This path can process an all-language content element while the page layout UI sends update[sys_language_uid] = 0 for the target column. The guard ensures that the copied record stays -1 instead of being downgraded to default language.

Missing coverage

Dedicated workspace copy coverage is missing for:

  • draft workspace state
  • publish of the copied workspace record
  • publish all workspace changes
  • discard of the copied workspace record

Proposed solution

Add functional regression coverage for the workspace variants of the existing language-all clipboard paste scenario.

The following tests should be added:

  • WorkspacesModify::copyLanguageAllContent()
  • WorkspacesPublish::copyLanguageAllContent()
  • WorkspacesPublishAll::copyLanguageAllContent()
  • WorkspacesDiscard::copyLanguageAllContent()

Existing live reference:

Acceptance criteria

  • Functional tests exist for all relevant workspace copy variants
  • The copied record remains sys_language_uid = -1 in all covered scenarios
  • Publish, publish-all, and discard behavior are asserted explicitly

Reviews 1

History 56

  1. Eric Harrer commented and changed attached Clipboard Paste Guard Entry in TYPO3.md <span data-processor="relativetime" data-value="2026-03-20T14:41:00+00:00" > 03/20/26, 14:41 </span>

    The attached document, which was generated by AI and curated by humans, contains the derivation path for the test coverage of the relevant guard entry. It is based on a fixed snapshot of the TYPO3 core repository and includes the producer workflows, request transformation, and the current coverage status. Today, at the Translation Handling Initiative meeting, we were able to follow and verify the entire process described therein.