#102034The treeConfig.startingPoints parameter does not work correctly in TYPO3 v 12 (Related to https://forge.typo3.org/issues/102015)
Description
Scenario:
1) A fresh TYPO3 v 12 installation
2) A page tree with 2 website root pages and a sysfolder (as in screenshot “Page_Tree.png”)
3) A Category Tree in the sysfolder (as in screenshot “Category_Tree.png”)
4) A backend usergroup named “Website A & B usergroup” that can manage both sites and has “Main Category 1” in Category Mounts (as in screenshot “Backend_Group.png”)
5) On “Website A” page -> Resources this TSConfig: TCEFORM.sys_category.parent.config.treeConfig.startingPoints=3 (where “3” is the uid of the first subcategory of “Main Category 1”
if the backend user associated with the backend usergroup tries to create a new category on the “Website A” page he should be able to see in the “parent” field the sub-category “Sub Category Root for Website A” and its subcategories thanks to the parameter TCEFORM.sys_category.parent.config.treeConfig.startingPoints=3 Instead he just sees only “Sub Category Root for Website A” (as in screenshot “New_Category_Creation.png”.
This is related to bug [102015]
Reviews 1
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". The changes above were merged or abandoned: read them before you start. How to create a patch
- Commit message
-
[BUGFIX] The treeConfig.startingPoints parameter does not work correctly in TYPO3 v 12 (Related to https://forge.typo3.org/issues/102015) Resolves: #102034 Releases: main
Related issues 2
Files 4
History 415
-
Andreas Kienast changed Related to #102015 <span data-processor="relativetime" data-value="2023-09-27T13:04:50+00:00" > 09/27/23, 13:04 </span>
-
Robert von Hackwitz commented <span data-processor="relativetime" data-value="2023-10-02T08:38:01+00:00" > 10/02/23, 08:38 </span>
-
Benni Mack changed Related to #96288 <span data-processor="relativetime" data-value="2024-12-11T16:14:16+00:00" > 12/11/24, 16:14 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 87780 status
NewUnder Review <span data-processor="relativetime" data-value="2025-01-16T15:35:28+00:00" > 01/16/25, 15:35 </span> -
Gerrit Code Review pushed patch set 6 for main to change 87780 <span data-processor="relativetime" data-value="2025-01-16T15:44:57+00:00" > 01/16/25, 15:44 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 87780 <span data-processor="relativetime" data-value="2025-03-04T07:49:22+00:00" > 03/04/25, 07:49 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 87780 <span data-processor="relativetime" data-value="2025-03-04T07:53:53+00:00" > 03/04/25, 07:53 </span>
-
Gerrit Code Review pushed patch set 9 for main to change 87780 <span data-processor="relativetime" data-value="2025-03-26T06:55:04+00:00" > 03/26/25, 06:55 </span>
-
Gerrit Code Review pushed patch set 10 for main to change 87780 <span data-processor="relativetime" data-value="2025-03-27T21:53:57+00:00" > 03/27/25, 21:53 </span>
-
Gerrit Code Review pushed patch set 11 for main to change 87780 <span data-processor="relativetime" data-value="2025-04-11T20:04:17+00:00" > 04/11/25, 20:04 </span>
-
Gerrit Code Review pushed patch set 12 for main to change 87780 <span data-processor="relativetime" data-value="2025-07-24T12:33:30+00:00" > 07/24/25, 12:33 </span>
-
Gerrit Code Review pushed patch set 13 for main to change 87780 <span data-processor="relativetime" data-value="2025-07-29T09:29:49+00:00" > 07/29/25, 09:29 </span>
-
Gerrit Code Review pushed patch set 14 for main to change 87780 <span data-processor="relativetime" data-value="2025-07-30T11:27:09+00:00" > 07/30/25, 11:27 </span>
-
Gerrit Code Review pushed patch set 15 for main to change 87780 <span data-processor="relativetime" data-value="2026-04-22T06:53:43+00:00" > 04/22/26, 06:53 </span>
-
Andreas Kienast changed status
Under ReviewNew <span data-processor="relativetime" data-value="2026-04-22T13:43:40+00:00" > 04/22/26, 13:43 </span>
Hi,
after a bit of investigation I think there is something wrong in
TYPO3\CMS\Backend\Security\CategoryPermissionsAspect around lines 68-80
foreach ($dataProvider->getStartingPoints() as $startingPoint) { if (!in_array($startingPoint, $categoryMountPoints)) { $shallRepopulateTree = true; break; } $uidsInRootline = $this->findUidsInRootline($startingPoint); if (empty(array_intersect($categoryMountPoints, $uidsInRootline))) { $shallRepopulateTree = true; break; } }With the for loop we check whether startingpoints are present in the user’s categorymounts,
but the starting points can be (as in my case) subcategories of a category mount points so the if statement is false, the variable $shallRepopulateTree is set to true and the cycle is interrupted, causing the reconstruction of the tree without the categories corresponding to the starting point