PackageManager caches absolute paths for different PATH_site
In some cases, when using a setup with several different domains and symlinks to the same folder, it can happen that the extension paths get resolved in a wrong way.
This happens in
when the cached extension path (absolute from the cached Packages) is stripped from the current PATH_site.
This results in something like "o3conf/ext/...", because the current PATH_site is longer than the cached version.
Either this should be addressed by default using the PATH_site in the caching identifier or, if this is too strict, by way of configuring it.
=> I made a patch using the old $GLOBALS['TYPO3_CONF_VARS']['EXT']['extCache'] variable
Please let me know what you think.
Updated by Helmut Hummel over 5 years ago
- Category changed from 1499 to 1594
- Status changed from New to Accepted
This has been resolved by including PATH_site in the cache identifier, so that we have different cache entries for different PATH_sites
However, we would greatly benefit from only storing the relative (to PATH_site) path in the package objects, so that we can remove the PATH_site from the cache identifier again and cache the information only once