Bug #28260
closed
"localconf.php is not found" after upgrade from 4.5.2 to 4.5.3
0%
Description
After Upgrade from 4.5.2 to 4.5.3 I get the following errors:
the frontend shows an error:
"Cannot find configuration. This file is probably executed from the wrong location."
the backend shows an error (http://www.example.com/typo3/index.php):
"Fatal error: Uncaught exception 'Exception' with message 'localconf.php is not found!' in /usr/share/typo3/typo3_src-4.5.3/t3lib/config_default.php:670 Stack trace: #0 /usr/share/typo3/typo3_src-4.5.3/typo3/init.php(206): require() #1 /usr/share/typo3/typo3_src-4.5.3/typo3/index.php(63): require('/usr/share/typo...') #2 {main} thrown in /usr/share/typo3/typo3_src-4.5.3/t3lib/config_default.php on line 670"
===============
How to reproduce:
- update all extensions
- clear caches
- delete temp files in typo3config dir
- change typo3_src symlink from 4.5.2 sources to 4.5.3 sources
error appears in frontend and backend
I have two typo3 installations. One of the threw the errors, the other one did not make any problems. Both, frontend and backend are working properly.
However, both installations were very similar, only some extensions were different.
The problem is reproducable in the following way:
- change typo3_src symlink back from 4.5.3 sources to 4.5.2 sources
=> both, frontend and backend work properly again
- change typo3_src symlink from 4.5.2 sources to 4.5.3 sources
=>both errors occur again
It seems to be a regression in the update. However I don't understand which difference in my two installations is responsible for the errors.
tested on debian 6, mysql 5.1, PHP 5.3.3-7+squeeze3
There are also other servers affected:
http://www.google.de/search?hl=de&biw=1600&bih=625&q=%27Exception%27+with+message+%27localconf.php+is+not+found+4.5.3&aq=f&aqi=&aql=&oq=
http://www.2bis10.de
Updated by Chris topher over 13 years ago
- Status changed from New to Needs Feedback
I could not find another page on the net with exactly the same problem: Many of the pages which you find using your google link show the error, because the BE is incorrectly called with "typo3_src/" in the path (and it is working without it), others (e.g. forum posts) are older so that they cannot affect TYPO3 4.5.3.
I guess that this is a configuration issue in the end. Please ask in the newsgroups. In the mailing lists people should be able to help you.
Updated by Thomas Mayer over 13 years ago
But when using typo3 4.5.2 everything is running fine. Therefore, the configuration should not be too bad.
For the moment, I downgraded to 4.5.2.
Updated by Stefan Neufeind over 13 years ago
Could it be you're running with some strange safe-mode-configuration or such, so that it might have no access to localconf.php? But no change from 4.5.2 to 4.5.3 that I know of should have triggered that.
Upgraded several 4.5.2 in the last months, all without problem. So I expect it's some kind of special setup on your side.
Updated by Thomas Mayer over 13 years ago
I found in the sources that the config_default.php (on line 670 ) tests for the file localconf.php with the file_exists() function. Using some testcode I figured out that the filename with absolute path (/var/www/example.com/wwwroot/typo3conf/localconf.php) was correct and the function returns true on my working installation but false on the other installation. Indeed there seems to be a restriction by apache or php.
=======================================
I aligned the apache vserver configurations of the working installation to the other one. Thereby, I mainly changed the entry
AllowOverride None
to
AllowOverride All
After apache restart, both backend and frontend work with 4.5.3
I wanted to reproduce the error by reverting to
AllowOverride None
But after apache restart, it is still working with "AllowOverride None". Unfortunately, I can't reproduce it that way.
For the moment, I can only say that the error occured directly after changing the typo3_src symlink to 4.5.3. And it disappeared after changing AllowOverride to All. Be it a regression bug, missing documentation or a configuration error - thanks for your help.
Updated by Chris topher over 13 years ago
- Status changed from Needs Feedback to Closed
Good to hear that you could solve this one.