Actions
Bug #4363
closedUsage of $GLOBALS['EXEC_TIME'] inappropriate in some places
Start date:
2009-08-27
Due date:
% Done:
100%
Estimated time:
TYPO3 Version:
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
Trying to follow some best practices, I had replaced quite a few calls to time() by the use of $GLOBALS['EXEC_TIME']. This has proven wrong in some situations. Indeed some scripts executed by the scheduler may last quite a while. When a task is finished, some calculations take place like the next execution date. In this case it is important for the calculations to be based on time(), otherwise their next execution date might already be in the past, if the task lasted longer than its own frequency (when using intervals).
Solution: revert a few uses of $GLOBALS['EXEC_TIME'] to time().
Updated by Francois Suter about 15 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Solved in r1143
Updated by Francois Suter over 12 years ago
- Status changed from Resolved to Closed
Updated by Michael Stucki almost 11 years ago
- Project changed from 739 to TYPO3 Core
- Category changed from scheduler to scheduler
Actions