[BUGFIX] Use different field for logging in EXT:scheduler 46/52846/2
authorGeorg Ringer <georg.ringer@gmail.com>
Fri, 21 Apr 2017 20:37:36 +0000 (22:37 +0200)
committerChristian Kuhn <lolli@schwarzbu.ch>
Thu, 18 May 2017 12:53:24 +0000 (14:53 +0200)
The public method Scheduler::log accepts an optional $code as 3rd
parameter. Add this information to the parameter $details of
BackendUserAuthentication::writelog as otherwise it will be
casted to an integer and its information will be lost.

Resolves: #80592
Releases: master, 8.7
Change-Id: Iab5f1d285976e9e88795ebbe75faff9f689b1a8c
Reviewed-on: https://review.typo3.org/52846
Tested-by: TYPO3com <no-reply@typo3.com>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
typo3/sysext/scheduler/Classes/Scheduler.php

index fad5a6a..f59d8c1 100644 (file)
@@ -460,7 +460,7 @@ class Scheduler implements \TYPO3\CMS\Core\SingletonInterface
     {
         // Log only if enabled
         if (!empty($this->extConf['enableBELog'])) {
-            $GLOBALS['BE_USER']->writelog(4, 0, $status, $code, '[scheduler]: ' . $message, []);
+            $GLOBALS['BE_USER']->writelog(4, 0, $status, 0, '[scheduler]: ' . $code . ' - ' . $message, []);
         }
     }