Issue Bug New Stale

#109941Page becomes its own parent after successive moves when initially moved as last child

Dominic Petit 06/01/26, 16:05 updated 06/01/26, 19:20

Description

When working in a workspace, moving an existing page multiple times can lead to data corruption where the page becomes its own parent (pid = t3ver_oid).
This results in:

  • The page disappearing from the page tree
  • An inconsistent page structure in the database
The issue only occurs under specific conditions:
  • The page being moved must initially exist in the Live workspace (already published)
  • The page is first moved as the last child of a parent page
  • The page is then moved again to another position, specifically between its parent page and its next sibling

*Initial page tree*
Root
├── Page A
├── Page B
└── Page C

*Step 1 – Move Page A under Page B (as LAST child)*
Root
├── Page B
│ └── Page A (moved here as last child)
└── Page C

*Step 2 — Move Page A between Page B and Page C*
Root
├── Page B
├── Page A ← expected position
└── Page C

*Actual result*
Root
├── Page B
└── Page C

(Page A disappears from tree)

In the database, the Page B has the same pid and t3ver_id

Additional note:

Attempting the same steps in the Live workspace correctly triggers the following error:
“Attempt to move pages:{pageId} to inside of its own rootline.”

In this case, the page remains visible and no corruption occurs.

The bug could not be reproduced in a TYPO3 v12 environment.

The behavior suggests that the move logic may rely primarily on visual adjacency in the tree rather than the actual hierarchical structure.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[BUGFIX] Page becomes its own parent after successive moves when initially moved as last child Resolves: #109941 Releases: main