95679[BUGFIX] Respect page visibility in rootline relations
Commit message
Test this change
Run a command in your clone of the TYPO3 Core. Then try what the change does and vote on Verified in Gerrit. How to review a patch
- Check out patch set 2
-
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/79/95679/2 && git checkout FETCH_HEAD - Cherry-pick onto main
-
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/79/95679/2 && git cherry-pick FETCH_HEAD
Review
-
Code review CR -1 Needs a vote
- Garvin Hicking +1
- Stefan Bürk -1
-
Verified V +1 Needs a vote
- Garvin Hicking +1
- core-ci +1 CI
Relation chain 2
- main 94993[FEATURE] Add table-specific hidden record visibility
-
95679 [BUGFIX] Respect page visibility in rootline relations This change
Merge conflicts 5
- main 94552[WIP][FEATURE] Passwordless passkey login for the backend
- main 96543[WIP][POC][TASK] Write and read records by the same rules and rights
- main 95723[!!!][TASK] Make VisibilityAspect constructor private
- main 66214[FEATURE] Allow text-track files for videos
- main 90107[FEATURE] Introduce database-only storage for OnlineMedia files
Issues 1
Files 4
Review log 911
-
Matthias Vogel uploaded patch set 1 09/07/26, 10:02
-
core-ci voted on patch set 1 V +1 09/07/26, 10:11 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/107998
-
Matthias Vogel marked it ready for review 09/07/26, 10:11
-
Matthias Vogel commented on patch set 1 CR -1 09/07/26, 10:21
-
Matthias Vogel uploaded patch set 2
CR -1V +109/07/26, 11:24 -
Matthias Vogel commented on patch set 2 09/07/26, 11:24
Important-110645-RespectPageVisibilityInRootlineRelations.rst:1ReplyDone -
core-ci voted on patch set 2 V +1 09/07/26, 11:32 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/108002
-
Stefan Bürk commented on patch set 2 CR -1 09/07/26, 13:09
-1 need to review this in detail ... -
Matthias Vogel commented on patch set 2 09/07/26, 14:09
should we backport to 14 or 13? -
Garvin Hicking commented on patch set 2 CR +1 V +1 10/19/26, 12:54
Reply Unresolved
I've looked this through with Matthias today and we did some intensive benchmarking. The "or" combination of course does have some performance penality, when the "bug"-case (true/false, false/true) comes into place. The numbers are in the forge issue, but I'd argue they are neglectible in the scope of miliseconds used even in larger setups given that we fix a bug with it. We also inspected whether modifying the index is necessary (we'd argue, yes) or if an additional index would help (little, and the extra costs in writing negates that by far). So I think we should merge this. I would go for main only and no backport, because: 1.) The scenario IMO feels edge-casey to me and I am unsure when this bug hits in production environments, also given we don't have a specific bugreport for it yet. 2.) It will force a sys_refindex DB table updated when running DB compare, which can take some time and in patchlevel releases people may not expect this 3.) Due to the possible impact on performance I'd rather try it out in a release-cycle rather than a patch-cycle. I'd like to wait for Stefans feedback before merging.Reply
(for me: no backport) -
Matthias Vogel commented on patch set 2 10/29/26, 09:25
Reply
Acknowledged
Important-110645-RespectPageVisibilityInRootlineRelations.rst:1