#107274Multiple category trees are not always visible
Description
Given the following TCA excerpt where the used variables are all integers
'categories' => [
'label' => 'LLL:' . <path_to_locallang.xlf> . 'event.categories',
'config' => [
'type' => 'category',
'minitems' => 1,
'treeConfig' => [
'startingPoints' => $rootCategory,
'appearance' => [
'maxLevels' => 2,
'nonSelectableLevels' => '0',
],
],
],
],
'daytime' => [
'label' => 'LLL:' . <path_to_locallang.xlf> . 'event.daytime',
'config' => [
'type' => 'select',
'renderType' => 'selectTree',
'foreign_table' => 'sys_category',
'treeConfig' => [
'parentField' => 'parent',
'startingPoints' => $rootDaytime,
'appearance' => [
'expandAll' => true,
'showHeader' => true,
'maxLevels' => 1,
'nonSelectableLevels' => '0',
],
],
],
],
'location' => [
'label' => 'LLL:' . <path_to_locallang.xlf> . 'event.location',
'config' => [
'type' => 'category',
'treeConfig' => [
'startingPoints' => $rootLocation,
'appearance' => [
'maxLevels' => 1,
'nonSelectableLevels' => '0',
],
],
],
],
the corresponding view in the backend is in most cases visible but sometimes not.
If they are not visible they are visible in most cases after a reload but it sometimes also took 2 to 3 reloads until they were visible.
The reason for the undisplay is seen in the console of the Google Chrome browser:
undisplayed-categories-due-to-unloadable-mutation-server.png
The MutationObserver cannot be loaded because selectTree hasn’t been loaded at that point of time.
So the MutationObserver should wait until selectTree is loaded to sort the issue out.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Files 1
History 3
-
Garvin Hicking commented and changed category status
NewNeeds Feedback 08/13/25, 10:55 -
Christian Huppert commented 09/15/25, 17:52
Thanks for the reply and apologies for answering a little late. I first had to wait for an answer from our project manager.
I took over that project so I cannot tell you why in one column the TCA type category was not used.
I followed your suggestion and used category also there and deployed it on our staging system.I now got feedback and it seems that this error only occurs in specific folders. My guess is that the occurrence of the
error depends on the folder’s content.Unfortunately I currently do not have the time to test the behaviour on TYPO3 12 LTS. But when I dedicate my time
soon onto this problem I will also give it a try with TYPO3 12 LTS and let you know.Thanks so far for your kind answer and suggestion!
-
Garvin Hicking commented and changed status
Needs FeedbackClosed 09/15/25, 18:47No worries, feel free to get in touch then. I do believe this should be fixed with the new tree in TYPO3v12. I believe the error you’re facing could be caused by longer request times on certain folders (if they have more sub-folders or many files in them) creating this timing issue.
I hope it’s ok with you to close the issue for now (due to the TYPO3v11 relation). If you later find out it’s also happening in v12 (or better yet, in v13) please do get back here or create a new issue and we’ll have a look!
Best regards,
Garvin
We no longer have community support for TYPO3v11 , so could you check this with v12 LTS?
Also, could you mention why you don’t use the type=category TCA types for all if the fields? That might also solve it?