Bug #19210
closed
Safe-mode conflict between Typo3 4.2 and PHP 5.2.6
0%
Description
After the ISP updated to PHP 5.2.6, the Typo3 backend was no longer vailable. Instead of the login screen, a PHP error came up reporting a safe-mode conflict. It turned out that PHP's parameter session.save_path was not initialised, and the default directory (/var/tmp) was not accessible in safe mode.
I needed to set "session.save_path to a new and accessible directory, in php.ini. When I did, everything worked again.
Unfortunately, not every ISP allows the user to make his own php.ini; and these ISPs more often than not have their servers in safe mode permanently and by default.
So it may be necessary to change typo3/install/index.php to include a call to session_save_path() with an appropriate value prior to calling start_session(). The value (path) to be used should be defined in the configuration.
(issue imported from #M9155)
Updated by Dmitry Dulepov over 16 years ago
I disagree. That path should be set by your hosting provider. TYPO3 should not do it because it does not know where session data should be stored on the server. It definitely cannot be inside web directory and TYPO3 does not write anything outside that directory.
If your hoster did not set session.save_path but enabled safe_mode, I doubt they are competent at web hosting.
When you work with TYPO3 or any other PHP product, you are responsible for providing proper PHP environment. This is your task. Products should not fix mistakes made by hosting companies.
Updated by Christian Kuhn over 15 years ago
Resolved, no change required. This is not a TYPO3 problem, the hoster must take care of a working php environment.
Updated by