Daniel Siepmann (Codappix)
cbeedaa908
* Use newest versions of actions.
* Use same naming for steps.
* Merge multiple jobs into one, for faster execution and less resource
consumption.
* Adopt `.gitattributes` to ignore new `.forgejo` folder instead of old
`.github` folder.
|
||
|---|---|---|
| .forgejo/workflows | ||
| Classes | ||
| Configuration | ||
| Tests | ||
| .gitattributes | ||
| .gitignore | ||
| .php-cs-fixer.dist.php | ||
| CHANGELOG.md | ||
| composer.json | ||
| LICENSE | ||
| phpstan-baseline.neon | ||
| phpstan.neon | ||
| phpunit.xml.dist | ||
| README.md | ||
| shell.nix | ||
Page specific TypoScript files for TYPO3
Hooks into TYPO3 system to load TypoScript files based on current TYPO3 page.
Why
There are a lot of legacy TYPO3 sites. Those often have multiple sys_template
records, loading TypoScript on specific pages.
This prevents tools like fractor to migrate the TypoScript.
Also many developers consider it best practice to not maintain TypoScript or Page TSconfig within the database. Instead it should be in the file system, allowing version control and deployment.
Usage
Once installed, the extension will check the following locations, within any active TYPO3 extension and include found files if any:
TypoScript Setup: Configuration/TypoScript/PageSpecific/<pageUid>/setup.typoscript
TypoScript Constants: Configuration/TypoScript/PageSpecific/<pageUid>/constants.typoscript
Page TSconfig: Configuration/TSconfig/PageSpecific/<pageUid>/Setup.tsconfig
TODO
- Implement use case for User TSconfig.