Issue Bug Closed

#109665Workspace: move content is broken. if in a second workspace the content element was already changed.

Matthias Vogel 04/21/26, 10:26 updated 08/11/26, 08:46

Description

To reproduce the Problem:

You need:
  • 2 Workspaces (should be empty/newly created)
  • 2 Content elements that are on the same page and column, in 2 Languages.

Change Text in one of the content elements in default language in Workspace A.
Go to Workspace B.
Move that Element to other position, on Drop/Save you will get:

[1.7]: Record "tt_content:51" you wanted to versionize was already a Version in Archive (record has an online ID)

This scenario was tested with TYPO3 14.3.0. (not tested in other versions)
It is most likely not the minimal reproduction example.

Reviews 3

History 69

  1. Christian Kuhn commented <span data-processor="relativetime" data-value="2026-05-02T15:31:11+00:00" > 05/02/26, 15:31 </span>

    Probably a regression from #106382. I’ll try to come up with something. Tests will verify if v13 is affected, too (probably: yes).

  2. Christian Kuhn commented <span data-processor="relativetime" data-value="2026-05-02T17:43:34+00:00" > 05/02/26, 17:43 </span>

    Ok.
    I played around with this for a while but was unable to actually reproduce the described scenario as-is.
    However, there is clearly a bug in DH that this guard ‘already a version in archive’ is fired too often because it is done after workspaceOL() call. I guess this will fix your scenario as well, but not 100% sure.
    We’ll go with a test and fix for the finding I had and hope it fixes your scenario as well. If that’s not the case, please create another issue and link to this one.

  3. Christian Kuhn commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-05-02T22:00:20+00:00" > 05/02/26, 22:00 </span>

    Applied in changeset commit:0cdb51144bc3388f1fe814d236d6bca810c42e3d.