#86941Logger instances in scheduler tasks are deserialized with outdated paths
Description
Scheduler serializes tasks and stores them in the database.
If these tasks store a logger instance (e.g. by using the LoggerAwareTrait), this instance will be serialized as well and will point to the wrong path, e.g. when TYPO3 is moved to a different folder
or path changes due to deployments.
This issue became much more prevalent with the addition of LoggerAwareTrait to \TYPO3\CMS\Scheduler\Task\AbstractTask
Now every single task will store outdated logger instances pointing to very likely broken directories
Reviews 4
Related issues 4
- Bug #86785Calling scheduler command on CLI throws error if not in /var/www/html
- Bug #87094A Symfony Console based scheduler task can't be executed and breaks the scheduler module
- Bug #87261Upgrade wizard for scheduler tasks with invalid Logger instance paths
- Bug #87780Extbase Task should call parents __sleep and __wakeup Methods