If you're working with TYPO3 v12 or later, you may have noticed significant changes in how assets are managed. The latest updates have introduced a new _assets folder within the public directory, replacing the older typo3conf structure. This transition is not just a cosmetic change; it brings enhanced security and improved asset management for your TYPO3 projects.
Why Migrate?
The migration from typo3conf to _assets is primarily driven by security improvements. With the introduction of the typo3/cms-composer-installers version 5, extensions are now installed in the vendor directory, making them inaccessible via direct HTTP requests. This means that sensitive files are better protected, reducing the risk of unauthorized access.
Key Steps for Migration
The blog post "Migrate typo3conf to _assets in Composer TYPO3 v12+" offers a detailed guide on how to execute this migration effectively. Here are some essential steps to consider:
Update References: Change any references in your Fluid templates, CSS, and JavaScript files that previously pointed to typo3conf/ext. Use the EXT:my_extension/Resources/Public/... notation to ensure compatibility with the new structure.
Adjust Build Pipelines: If you have frontend build pipelines that wrote files into typo3conf/ext, update them to point to your extension’s source directory instead.
Utilize Relative Links: For internal references, use relative paths to avoid hardcoding links that may break during migration.
Leverage TypoScript and Fluid: Use TypoScript and Fluid to create dynamic paths that reference your assets correctly.
Test Thoroughly: After making these changes, ensure that your site functions as expected. Clear caches and check that all assets are loading correctly.
Conclusion
Migrating to the _assets structure not only enhances security but also streamlines your TYPO3 asset management. For a comprehensive guide and more detailed instructions, check out the full blog here [Migrate typo3conf to _assets in Composer TYPO3 v12+ ].