TYPO3 Core

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!