Bug #61317

PackageManager caches absolute paths for different PATH_site

Added by Nils Blattner over 6 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
composer
Target version:
-
Start date:
2014-09-02
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Hi there

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
\TYPO3\CMS\Core\Utility\PathUtility::stripPathSitePrefix()
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.

Cheers Nils


Files

20140902-PackageManager.php (753 Bytes) 20140902-PackageManager.php Nils Blattner, 2014-09-02 15:44

Related issues

Related to TYPO3 Core - Bug #57950: Respect PATH_site while creating cacheIdentifierClosed2014-04-15

Actions
Related to TYPO3 Core - Bug #57601: Upgrading 6.2: PHP Fatal error: Uncaught exception 'TYPO3\\Flow\\Package\\Exception\\PackageStatesFileNotWritableExceptionClosed2014-04-03

Actions
Related to TYPO3 Core - Bug #53215: Rename symlink of typo3_src results in fatal errorClosed2013-10-30

Actions
#1

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

#2

Updated by Helmut Hummel over 5 years ago

  • Priority changed from Must have to Could have

Would be nice to have this to avoid multiple caches to be written

#3

Updated by Benni Mack over 4 years ago

How about we only write the paths relative to the project root in the cache files? This way they are completely portable..

#4

Updated by Benni Mack about 2 years ago

  • Status changed from Accepted to Closed

Fixed with TYPO3 v9

Also available in: Atom PDF