Global Sysfolders + Contents are not translatable anymore since TYPO3 10
For multitree instances we often used a global sysfolder to store some global informations (cookie services, subsidiaries, news,...). Up until TYPO3 9 the sysfolder and its contents could be translated if there were language records on pid 0.
Starting form TYPO3 10, the site configuration is checked also for available translations. As there is no site configuration for the sysfolder it won't be translatable anymore.
Please see attached screenshots which are showing the difference.
Updated by Daniel Haupt 5 months ago
Georg Ringer wrote in #note-4:
closing the issue. this is intended and it might be that it will be even more restricted in future
Issue #90948 seems to be related or targeting the same issue.
In case no site configuration has been created for a tree, all language records are shown. (https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/9.4/Feature-85164-AvailableLanguagesRespectsSiteConfigurationSettings.html)
So creating a dummy site configuration is the intended new way?
Thge Site configuration is automatically created for new pages on root level (https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/10.1/Feature-89142-CreateSiteConfigurationIfPageIsCreatedOnRootLevel.html). This could be done for folders too, right?