#110894Copying a page moves nested inline records to an unrelated page
Description
No description.
Reviews 2
History 24
-
Gerrit Code Review pushed patch set 1 for main to change 96324 status
NewUnder Review <span data-processor="relativetime" data-value="2026-10-02T16:38:15+00:00" > 10/02/26, 16:38 </span> -
Gerrit Code Review pushed patch set 1 for 14.3 to change 96346 <span data-processor="relativetime" data-value="2026-10-03T07:04:33+00:00" > 10/03/26, 07:04 </span>
-
Benni Mack commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-10-03T07:10:09+00:00" > 10/03/26, 07:10 </span>Applied in changeset commit:8cda2bd146eeb6e42f5674a3465cb3eb3e08c189.
When you copy a page whose inline records have inline records of their own, some of those nested records can end up on another page. On the copy they then seem lost.
It only happens if the workspaces extension is installed and the uid of a copied first-level record matches the uid of a page that has a workspace version. That’s why it looks random.
Steps to reproduce
1. Install the workspaces extension, and an extension that adds an inline field to pages whose records have inline children themselves (e.g. page → hotels → offers).
2. Create page A with one hotel, and give that hotel one offer.
3. In a workspace, edit any other page B, for example by changing its title, so B gets a workspace version. Note the uid of that workspace version.
4. Make sure the next new hotel gets exactly that uid. In a test system, set the auto-increment value of the hotel table.
5. Copy page A.
6. Look at the offer of the copied hotel, for example with the List module or in the database.
Expected: the copied offer is on the copied page.
Actual: the copied offer is on page B.