#109665Workspace: move content is broken. if in a second workspace the content element was already changed.
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
Related issues 1
History 69
-
Garvin Hicking changed category <span data-processor="relativetime" data-value="2026-04-23T15:24:12+00:00" > 04/23/26, 15:24 </span>
-
Christian Kuhn changed Related to #106382 <span data-processor="relativetime" data-value="2026-05-02T15:30:16+00:00" > 05/02/26, 15:30 </span>
-
Christian Kuhn commented <span data-processor="relativetime" data-value="2026-05-02T15:31:11+00:00" > 05/02/26, 15:31 </span>
-
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. -
Gerrit Code Review pushed patch set 3 for main to change 93912 status
NewUnder Review <span data-processor="relativetime" data-value="2026-05-02T19:24:50+00:00" > 05/02/26, 19:24 </span> -
Gerrit Code Review pushed patch set 1 for 14.3 to change 93921 <span data-processor="relativetime" data-value="2026-05-02T21:13:45+00:00" > 05/02/26, 21:13 </span>
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 93922 <span data-processor="relativetime" data-value="2026-05-02T21:14:00+00:00" > 05/02/26, 21:14 </span>
-
Christian Kuhn commented and changed status
Under ReviewResolved done0 %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.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-08-11T08:46:50+00:00" > 08/11/26, 08:46 </span>
Probably a regression from #106382. I’ll try to come up with something. Tests will verify if v13 is affected, too (probably: yes).