Issue Bug Closed

#19210Safe-mode conflict between Typo3 4.2 and PHP 5.2.6

H. Hahn 08/11/08, 21:32 updated 10/02/18, 12:29

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)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.