Bug #88190
closedScheduler not running when php_sapi_name is cgi-fcgi
0%
Description
Was discovered in Typo3 8.7.24
- php_sapi_name() on the system reports 'cgi-fcgi'
- \typo3\sysext\core\Classes\Console\CommandApplication.php::97 checks for: if (php_sapi_name() !== 'cli') {
=> The check should be: if (substr(php_sapi_name(), 0, 3) !== 'cgi') {
=> similar to typo3\sysext\backend\Classes\Console\Application.php::99
Updated by Bastian Bringenberg over 5 years ago
- Project changed from 9 to TYPO3 Core
- TYPO3 Version set to 8
Changed Project.
Updated by Christian Ebert over 5 years ago
Please close the issue. I think the problem is the hosting environment not providing the php-cli correctly.
Ebert no-lastname-given wrote:
Was discovered in Typo3 8.7.24
- php_sapi_name() on the system reports 'cgi-fcgi'
- \typo3\sysext\core\Classes\Console\CommandApplication.php::97 checks for: if (php_sapi_name() !== 'cli') {=> The check should be: if (substr(php_sapi_name(), 0, 3) !== 'cgi') {
=> similar to typo3\sysext\backend\Classes\Console\Application.php::99
Updated by Hartmut Steglich over 5 years ago
... the problem is the hosting environment not providing the php-cli correctly.
I can confirm this for the German hoster strato.de which uses "cgi-fcgi" and TYPO3 9.5