Project

General

Profile

Actions

Task #33203

closed

System Status Update (reports) - different readings on PHP Memory Limit etc.

Added by Dennis Hoffland over 12 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
scheduler
Target version:
-
Start date:
2012-01-15
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

When the Scheduler is triggered directly by a .php script (instead of a cron job. See posting on TYPO3 English Archive: January 2012), it produces other results than:
  • the System Status Update (reports) task run manually from the Scheduler at the TYPO3 BE,
  • the Status Report (Admin Tools > Reports), and
  • phpinfo() (Admin Tools > Install).

These results should of course be consistent.

Most likely cause of the different readings on PHP settings: in case of the .php script the Scheduler checks against the values of the php.ini file at the PHP CLI instead of the 'normal' php.ini (See also TYPO3 English Archive: January 2012 and http://forge.typo3.org/issues/25691 ).


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #25691: Test-Task should check for PHP CLI Memory-LimitClosed2011-02-21

Actions
Related to TYPO3 Core - Bug #56569: SystemEnvironment check shouldn't give error on fileUpload values in CLI contextClosed2014-03-05

Actions
Actions

Also available in: Atom PDF