Task #103896
closed
Implement User TSconfig provider for profiles and sites
0%
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.
Updated by Daniel Siepmann about 1 month ago
- Related to Epic #103630: Site sets: Composable (sub)set's of site configuration, shippable in extensions added
Updated by Daniel Siepmann about 1 month ago
- Related to Feature #101807: Add centralized way to load User TSconfig added
Updated by Daniel Siepmann about 1 month ago
- Related to Feature #96614: Add centralized way to load PageTsConfig added
Updated by Daniel Siepmann about 1 month ago
- Related to Task #103522: Implement Page TSconfig provider for profiles and sites added
Updated by Georg Ringer about 1 month ago
- 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?
Updated by Daniel Siepmann about 1 month ago
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.
Updated by Georg Ringer about 1 month ago
- Status changed from Needs Feedback to Accepted
Updated by Georg Ringer 2 days ago
- Status changed from Accepted to Rejected
Hey,
I discussed this with Christian Kuhn and we came to the conclusion that we don't want to go this way because the user just doesn't belong to a site/page.
It is ok to have a different configuration for that, just as e.g. also permissions are configured on a different place.
if you don't agree, feel free to contact me via slack!
Updated by Daniel Siepmann 2 days ago
No I'm fine with either decision. I guess I already communicated my point about a streamlined experience.
But I'll not argue about that and of course accept to your decision.
Updated by Christian Kuhn 2 days ago
- Related to Feature #103996: Introduce Page TSconfig for FileList-module added
Updated by Christian Kuhn 2 days ago
Note this also easily raises chicken-egg issues: usertsconfig already allows to overload pagetsconfig. When we additionally bind usertsconfig to pages or sites, this creates a huge load-order mess. I strongly recommend to not further mix this up.