94311[BUGFIX] Respect pid=0 and rooLevelRestriction in DH::versionizeRecord
Commit message
Review
-
Code review CR 0
-
Verified V 0
- core-ci +1 CI
Issues 2
Files 2
Review log 911
-
Andreas Häfner uploaded patch set 1 06/04/26, 08:10
-
core-ci voted on patch set 1 V +1 06/04/26, 08:17 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/102939
-
Andreas Häfner uploaded patch set 2
V +106/04/26, 08:50 -
core-ci voted on patch set 2 V +1 06/04/26, 09:02 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/102940
-
Andreas Häfner commented on patch set 2 06/04/26, 09:02
-
Andreas Häfner commented on patch set 2 06/04/26, 09:47
Unresolved
A possible approach could be, to populate a default page record array in case pid=0 so that BackendUserAuthentication::isInWebMount and other can work with usable data. That way rootPage could be handled as each other page without extra handling. -
Benni Mack commented on patch set 2 06/11/26, 07:47
This one is similar, right? https://review.typo3.org/c/Packages/TYPO3.CMS/+/91338 -
Andreas Häfner commented on patch set 2 06/11/26, 08:09
Yes. Seems to solve same issue -
Oliver Hader commented on patch set 2 06/24/26, 18:22
Unresolved
This patch and the referenced patch actually would fix the problem and tackle the right locations in the code. However, I tried to take it a step further - basically to avoid checking for the root-level restriction in the schema again and again, but to make that explicit and centralize the handling. So, I added a new enum case `VirtualRecord::RootPage`. → see it in action at https://review.typo3.org/c/Packages/TYPO3.CMS/+/94573 -
Andreas Häfner commented on patch set 2 06/25/26, 05:27
Unresolved
I Like the approach with VirtualRecord. -
Benni Mack abandoned the change 07/16/26, 14:03
fixed in latest versions.
Unresolved