The new generation of typo3/cms-composer-installers u

We could... make <a href="https://docs.

Relates: <a class="issue-link js-issue-link" data-error-text="Failed to load title" da

typo3/cms-composer-installers:^4 compatibility will need some work about extension-cookieman HOT 4 OPEN

jonaseberle commented on June 30, 2024

typo3/cms-composer-installers:^4 compatibility will need some work

from extension-cookieman.

Comments (4)

jonaseberle commented on June 30, 2024

See https://forge.typo3.org/issues/99203 for TypoScript solutions and comments on https://typo3.slack.com/archives/C02JDFFLBEW/p1669449850484169

from extension-cookieman.

jonaseberle commented on June 30, 2024

We could...

make inject a string / stdWrap (probably with recommendation to use {path : EXT:...})
- Requires users to update their cookieman configuration for injected local URLs.
- Does not solve the greater problem of referencing arbitrary assets from JS or from an external system.
- Could benefit from cache-busting param feature (probably only v12+)
have a middleware that keeps /typo3conf/ext/.../Resources/Public/... working by either readfile()ing or forwarding (307) to the final location. For performance it could transparently add symlinks on the fly if the file system is writable (to be used for consecutive requests).
- Benefits all use cases that want to continue using known local URLs.
- For sending via PHP: Setting headers adds an unnecessary layer and potential source of problems. Doing a local request for passing through web server's headers could be a performance problem or fail in some environments.
- For forwarding: Needs validation if it works reliably with all types of assets in all browsers (should in theory).
have a composer plugin that manages symlinks for installed/uninstalled typo3-cms-extension packages.
- Benefits all use cases that want to continue using known local URLs.
- composer-only is not a problem: the new folder structure only applies to composer-installs
- it might be non-trivial to replicate https://github.com/TYPO3/typo3/blob/12.1/typo3/sysext/core/Classes/Composer/PackageArtifactBuilder.php#L269 outside of a TYPO3 context (the exact way of building the _asset path is not public API AFAIK)