Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TASK] Use GeneralUtility::getFileAbsFileName for resolving web assets #225

Merged
merged 1 commit into from
Dec 17, 2021
Merged

[TASK] Use GeneralUtility::getFileAbsFileName for resolving web assets #225

merged 1 commit into from
Dec 17, 2021

Commits on Dec 16, 2021

  1. [TASK] Use GeneralUtility::getFileAbsFileName for resolving web assets

    Due to upcoming changes in typo3/cms-composer-installers v4.0.0
    (currently available as RC1), composer packages are not linked
    anymore to public folder typo3conf/ext/extension_name/.
    
    As a result, web assets need to be resolved accordingly, see
    https://github.com/TYPO3/CmsComposerInstallers/releases/tag/v4.0.0-RC1
    
    In this particular scenario the change is simple, but (now) with
    a corresponding distinction between "extension path" and "public
    extension resources path":
    * `PathUtility::getAbsoluteWebPath('EXT:extension_name/')` resolves
      to corresponding (private) folder in Composer `vendor/` folder
    * `PathUtility::getAbsoluteWebPath('EXT:extension_name/Resources/Public')`
      resolves to (virtual) public path `typo3conf/ext/`
    
    Fixes: https://forge.typo3.org/issues/96374
    ohader committed Dec 16, 2021
    Configuration menu
    Copy the full SHA
    b6a0954 View commit details
    Browse the repository at this point in the history