#99203Re-introduce easy possibility to add paths via TypoScript
Description
Problem/Description
When TYPO3 composer installers v4 and v5 are the defacto standard in the next couple of months a simple TypoScript function OR stdWrap function OR cObject would help a lot when an integrator want to include any™ kind of Text/HTML/… e.g. in the <HEAD /> section of the HTML document.
An example
> (found in an long living TYPO3 project where the next TYPO3 version must use TYPO3 Composer Installer v5)
page = PAGE
page {
headerData {
100 = TEXT
100.value = <link rel="preload" as="font" type="font/woff2" href="typo3conf/ext/theme/Resources/Public/Fonts/Inter-Regular.woff2" crossorigin>
110 = TEXT
110.value = <link rel="preload" as="font" type="font/woff2" href="typo3conf/ext/theme/Resources/Public/Fonts/Inter-SemiBold.woff2" crossorigin>
120 = TEXT
120.value = <link rel="preload" as="font" type="font/woff2" href="typo3conf/ext/theme/Resources/Public/Fonts/orion-font.woff2" crossorigin>
}
}
> Maybe I forgot all my TypoScript skills, but actually I don’t know how to easily migrate that to make it bulletproof™
1. ToDo(s)
- It would be very helpful if an integrator can simple use the
EXT:...syntax that the resulting (somehow cryptic) path get’s adopted.
Acceptance Criteria
A TYPO3 integrator should have a straight forward solution to add paths for files (in the frontend) which supports the EXT:... syntax.
Reviews 2
Related issues 5
- Feature #99340Add stdWrap to config.additionalHeaders.10.header
- Feature #103617Cache busting parameter for f:uri.resource via createVersionNumberedFilename()
- Task #104640Highlight relevant code snippets in changelog
- Bug #104807getText path broken for extension paths in v12
- Bug #105403f:image and cache busting issue