#96288TCA type category not editable/shown for editors if startingPoints are set
Description
If startingPoints are set, the categories won’t be shown for editor users. When removing startingPoints, all categories are shown, even for editor.
Using it like this:
'categories' => [
'exclude' => true,
'label' => $langFile . $table . '.categories',
'config' => [
'type' => 'category',
'treeConfig' => [
'startingPoints' => '###SITE:categories.product###',
]
]
]
Setting an int value instead of site-config has the same effect. Also configuring it with tsconfig settings.
For the admin user everything works fine. Also checked user settings for editor, looks good to me.
Reviews 3
Related issues 4
- Bug #96397Category starting points don't accept CSV
- Bug #102015Incorrect behavior of TCEFORM treeConfig.startingPoints
- Bug #102034The treeConfig.startingPoints parameter does not work correctly in TYPO3 v 12 (Related to https://forge.typo3.org/issues/102015)
- Bug #106559No access to sub categories when using category_perms + treeConfig.startingPoints
History 1333
Show 78 earlier messages
-
Andreas Kienast commented <span data-processor="relativetime" data-value="2021-12-20T13:56:04+00:00" > 12/20/21, 13:56 </span>
-
Andreas Kienast changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2021-12-20T13:56:09+00:00" > 12/20/21, 13:56 </span> -
Andreas Kienast commented <span data-processor="relativetime" data-value="2021-12-20T14:13:44+00:00" > 12/20/21, 14:13 </span>
I’ve created https://forge.typo3.org/issues/96397 and pushed a patch to https://review.typo3.org/c/Packages/TYPO3.CMS/+/72738, can you please check whether this solves your issue?
Kind regards
Andreas -
Benni Mack changed Related to #96397 <span data-processor="relativetime" data-value="2021-12-20T15:51:33+00:00" > 12/20/21, 15:51 </span>
-
David Hoeckele commented <span data-processor="relativetime" data-value="2022-01-03T12:44:30+00:00" > 01/03/22, 12:44 </span>
Thanks for your reply – i have just configured one single integer value.
It’s only an issue with the editors – the category selection appears empty if an startingPoint is configured. As an admin user i can see the categories with all possible variants (site config, TCA, TSconfig) and it works as expected …
-
Cyrill Gsell commented <span data-processor="relativetime" data-value="2022-03-02T12:15:45+00:00" > 03/02/22, 12:15 </span>
I have the same problem, it happens when you set a spartingPoint in the TCA and set the same starting point as a category mount in the backend user group. I think the problem occurs at this point TYPO3\CMS\Backend\Security\CategoryPermissionsAspect::lookUpCategoryMountPointInTreeNodes; only the child nodes are checked if they are in one of the selected category mount points but not the parent node (startingPoint).
-
Florian Rival commented <span data-processor="relativetime" data-value="2023-01-30T12:26:21+00:00" > 01/30/23, 12:26 </span>
Same problem for me when I set the startingPoints through TCEFORM :
TCEFORM.tx_mytable.domaine.config.treeConfig.startingPoints = 10
but if I set two categories :
TCEFORM.tx_mytable.domaine.config.treeConfig.startingPoints = 10, 20
The problem disappears.
In method DatabaseTreeDataProvider::loadTreeData() , implementation is different if you have one startingPoint category or multiples startingPoints.With one startingPoint, only sub-categories are stored in $this->treeData.
With multiple startingPoints, only TCEFORM.tx_mytable.domaine.config.treeConfig.startingPoints are stored in $this->treeData. -
Gerrit Code Review pushed patch set 1 for main to change 77642 status
Needs FeedbackUnder Review <span data-processor="relativetime" data-value="2023-01-30T16:31:50+00:00" > 01/30/23, 16:31 </span>
-
Gerrit Code Review pushed patch set 2 for main to change 77642 <span data-processor="relativetime" data-value="2023-02-05T19:51:05+00:00" > 02/05/23, 19:51 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 77642 <span data-processor="relativetime" data-value="2023-03-06T10:36:38+00:00" > 03/06/23, 10:36 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 77642 <span data-processor="relativetime" data-value="2023-05-03T09:33:43+00:00" > 05/03/23, 09:33 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 77642 <span data-processor="relativetime" data-value="2024-10-15T10:07:50+00:00" > 10/15/24, 10:07 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 77642 <span data-processor="relativetime" data-value="2024-10-18T13:55:37+00:00" > 10/18/24, 13:55 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 77642 <span data-processor="relativetime" data-value="2024-11-20T17:00:14+00:00" > 11/20/24, 17:00 </span>
-
Benni Mack changed Related to #102034 <span data-processor="relativetime" data-value="2024-12-11T16:14:16+00:00" > 12/11/24, 16:14 </span>
-
Andreas Kienast changed Related to #102015 <span data-processor="relativetime" data-value="2025-01-16T13:37:38+00:00" > 01/16/25, 13:37 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 87780 <span data-processor="relativetime" data-value="2025-01-16T15:35:27+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:54+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:20+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:51+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:01+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:54+00:00" > 03/27/25, 21:53 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 77642 <span data-processor="relativetime" data-value="2025-03-28T11:47:49+00:00" > 03/28/25, 11:47 </span>
-
Gerrit Code Review pushed patch set 9 for main to change 77642 <span data-processor="relativetime" data-value="2025-03-28T11:47:56+00:00" > 03/28/25, 11:47 </span>
-
Gerrit Code Review pushed patch set 11 for main to change 87780 <span data-processor="relativetime" data-value="2025-04-11T20:04:14+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:28+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:47+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:08+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:42+00:00" > 04/22/26, 06:53 </span>
-
Andreas Kienast changed status
Under ReviewNew <span data-processor="relativetime" data-value="2026-04-22T13:43:25+00:00" > 04/22/26, 13:43 </span> -
Florian Rival commented and changed TYPO3 Version
1113 <span data-processor="relativetime" data-value="2026-06-02T11:04:20+00:00" > 06/02/26, 11:04 </span>This bug is still present with version 13, it’s a regression and it exist since 4 years now.
I’ve seen that the patch was rejected with reason “Stale and hard to test” but it should be corrected.
As a workaround, we can add a fake category id at startingPoints, instead of:
TCEFORM.tx_mytable.categories.config.treeConfig.startingPoints = 10add a false starting point like ‘-1’ or ‘0’:
TCEFORM.tx_mytable.categories.config.treeConfig.startingPoints = 10, -1But it’s just a workaround.
-
Benni Mack changed Related to #106559 <span data-processor="relativetime" data-value="2026-11-13T08:52:55+00:00" > 11/13/26, 08:52 </span>
-
Benni Mack commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-11-13T08:53:12+00:00" > 11/13/26, 08:53 </span>Fixed with #106559
Hello,
can you please tell how
SITE:categories.productis defined? Do you use by chance a comma-separated value?Kind regards
Andreas