Task #103896
open
Implement User TSconfig provider for profiles and sites
Added by Daniel Siepmann about 1 month ago.
Updated about 1 hour ago.
Sprint Focus:
Needs Decision
Description
Just like #103522 introduced Page TSconfig, it would be beneficial if we would add User TSconfig as well, in order to provide a streamlined experience.
It is confusing if TypoScript and Page TSconfig but not User TSconfig will be provided via Site Sets.
#101807 already introduced auto loading of User TSconfig from extensions, just like done via #96614 for Page TSconfig.
- Related to Epic #103630: Site sets: Composable (sub)set's of site configuration, shippable in extensions added
- Related to Feature #101807: Add centralized way to load User TSconfig added
- Related to Feature #96614: Add centralized way to load PageTsConfig added
- Related to Task #103522: Implement Page TSconfig provider for profiles and sites added
- Description updated (diff)
- Status changed from New to Needs Feedback
as usertsconfig is not bound to a site but to the user I am unsure if we should really do that?
An extension can provide a file for user tsconfig that is auto loaded #101807.
It was possible for years to load user tsconfig from ext_localconf.php via TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addUserTSConfig()
It is very confusing for users if one API and mechanism is not streamlined. Many installations also only have one Site and one now needs to know and remember which part is available via new sites, and which is not.
- Status changed from Needs Feedback to Accepted
- Sprint Focus set to Needs Decision
Also available in: Atom
PDF
Updated by 
Updated by