Bug #29901: t3lib_autoloader::getAutoloadCacheIdentifier should respect PATH_site - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Bug #29901

closed

t3lib_autoloader::getAutoloadCacheIdentifier should respect PATH_site

Added by Frederic Gaus about 13 years ago. Updated about 7 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Category:

Target version:

4.6.0

Start date:

2011-09-16

Due date:

% Done:

100%

Estimated time:

1.00 h

TYPO3 Version:

4.6

PHP Version:

5.3

Tags:

Complexity:

easy

Is Regression:

Sprint Focus:

Description

When installing the whole TYPO3 site on a different server (e.g. changing provider or deploying dev to live), you normally move the whole webroot to another server.

But with TYPO3 4.6 and caching framework enabled this causes a fatal error on the new host because the autoloader stores the classes inside the registry with an absolute path.

Example:
Warning: require(/var/www/web9/t3lib/utility/class.t3lib_utility_versionnumber.php): failed to open stream: No such file or directory in /var/www/typo3/typo3_src-master-mount/t3lib/class.t3lib_div.php on line 5089 Fatal error: require(): Failed opening required '/var/www/web9/t3lib/utility/class.t3lib_utility_versionnumber.php' (include_path='.:/usr/share/php:/usr/share/pear:/var/www/typo3-46/typo3/contrib/pear/') in /var/www/typo3/typo3_src-master-mount/t3lib/class.t3lib_div.php on line 5089

This fatal error occures in frontend, backend and install tool. Deleteing typo3conf/temp_CACHED* is not helping. This could confuse many users not that familier with TYPO3.

It would be easy to fix when t3lib_autoloader::getAutoloadCacheIdentifier would respect TYPO3_site, too.