Review main Merged

97249[BUGFIX] Keep category tree for mounted starting points

Oli Bartsch CR +2 V +2 Normal +133 −4 updated 11/07/26, 19:03

Commit message

When multiple tree starting points were introduced, the category
permission check changed from "the starting point or one of its parents
is a category mount" to "the starting point and one of its parents are
category mounts". A mounted starting point without a mounted parent,
e.g. a top-level category, therefore always triggered repopulating the
tree from the mount points. With a single starting point, that starting
point is the root node itself and is never found among its own child
nodes, so editors only saw the bare root without any sub categories.
Likewise, a starting point below a category mount was not accepted,
so its sub categories were not shown either.

A starting point which is a category mount itself is now accepted
right away, and the rootline is only checked for starting points that
are not mounted. Since unmounted starting points such as 0 are now
looked up, a missing database row is handled.

Review

  • Code review CR +2 Done
    • Georg Ringer +2
    • Benni Mack +1
    • Simon Schaufelberger +1
  • Verified V +2 Done
    • Georg Ringer +2
    • Benni Mack +1
    • Simon Schaufelberger +1
    • core-ci +1 CI

Issues 1

Files 3

Review log 68

  1. Oli Bartsch uploaded patch set 1 10/31/26, 09:12

  2. core-ci voted on patch set 1 V +1 10/31/26, 09:20 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/112944

  3. Oli Bartsch uploaded patch set 2 V +1 10/31/26, 09:39

  4. core-ci voted on patch set 2 V +1 10/31/26, 09:47 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/112947

  5. Benni Mack voted on patch set 2 CR +1 V +1 11/01/26, 20:45

  6. Simon Schaufelberger voted on patch set 2 CR +1 V +1 11/06/26, 09:19

  7. Georg Ringer voted on patch set 2 CR +2 V +2 11/06/26, 09:28

  8. Georg Ringer merged patch set 3 11/07/26, 19:03