#106251DB mount lost when page moved in draft workspace
Description
BE users that have only access to a draft workspace suddenly lose their DB mount when that very page gets moved among its parents subpages (different sorting, same pid!) and that change is still unpublished.
- Create a two level pagetree:
- rootpage ‘root’
- subpage ‘sub a’
- subpage ‘sub b’
- Create a be_group
- set DB mount to page ‘sub a’
- remove live-editing permission
- name it ‘draft editors’
- Create a sys_workspace record
- no DB mount (so it’s got a global scope)
- add ‘draft editors’ as member or admin.
- Create a be_user ‘intern’, give them ‘draft editors’ as group
- log in as ‘intern’, find ‘sub a’ in the page tree
=> All good!
- as admin change the sorting of ‘sub a’ and ‘sub b’ in the draft workspace, don’t publish!
- log in as ‘intern’, empty page tree ;-(
=> That’s not good!
- as admin change the sorting of ‘sub a’ and ‘sub b’ in the draft workspace, do publish that change!
- log in as ‘intern’, find ‘sub a’ in the page tree
=> All good again!
First experienced this bug in TYPO3 11, but can be reproduced in latest main a.k.a 14-dev branch too!
Reviews 3
History 59
-
Philipp Kitzberger changed description <span data-processor="relativetime" data-value="2025-02-25T22:03:26+00:00" > 02/25/25, 22:03 </span>
-
Georg Ringer changed status
NewAccepted <span data-processor="relativetime" data-value="2025-02-26T07:36:18+00:00" > 02/26/25, 07:36 </span> -
Gerrit Code Review pushed patch set 1 for main to change 88362 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2025-02-26T07:49:28+00:00" > 02/26/25, 07:49 </span> -
Gerrit Code Review pushed patch set 2 for main to change 88362 <span data-processor="relativetime" data-value="2025-02-26T19:41:17+00:00" > 02/26/25, 19:41 </span>
-
Benni Mack commented and changed status
Under ReviewNeeds Feedback <span data-processor="relativetime" data-value="2025-04-08T09:50:11+00:00" > 04/08/25, 09:50 </span> -
Philipp Kitzberger commented <span data-processor="relativetime" data-value="2026-02-07T13:33:37+00:00" > 02/07/26, 13:33 </span>
We’ve upgraded the project in question from v11 to v13 and are still successfully using patchset 2 to fix this problem.
> I assume this happens / happened also when the root page is modified by an admin, or only when moved?
I can only reproduce this with a draft-change on sorting or pid of the DB mounted page.
Interestingly enough: the ‘intern’ can successfully publish the “moving operation” of the DB mounted page (without having ro or rw access to its parent and/or target page!)
-
Gerrit Code Review pushed patch set 1 for main to change 96832 status
Needs FeedbackUnder Review <span data-processor="relativetime" data-value="2026-10-18T16:27:33+00:00" > 10/18/26, 16:27 </span> -
Gerrit Code Review pushed patch set 1 for 14.3 to change 97039 <span data-processor="relativetime" data-value="2026-10-23T04:44:06+00:00" > 10/23/26, 04:44 </span>
-
Benni Mack commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-10-23T04:50:10+00:00" > 10/23/26, 04:50 </span>Applied in changeset commit:e41b5236e733fa341684f42abaade10fd8cb3dd9.
Hey Philipp,
we have created a patch for this but it showed that the current behavior is correct. I assume this happens / happened also when the root page is modified by an admin, or only when moved?