Project

General

Profile

Actions

Bug #79141

closed

Unable to create scheduler tasks: Call to a getNotificationEmail() on null

Added by Christian Weiske over 7 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Category:
scheduler
Target version:
-
Start date:
2017-01-03
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
7
PHP Version:
7.0
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

On a TYPO3 7.6.10 instance I cannot create scheduler tasks. Whenever trying to save a new scheduler task, I get an exception:

Call to a member function getNotificationEmail() on null
Error thrown in file
/var/www/site/htdocs/typo3_src/typo3/sysext/reports/Classes/Task/SystemStatusUpdateTaskNotificationEmailField.php in line 49.

called in TYPO3\CMS\Scheduler\Controller\SchedulerModuleController::editTaskAction()
$additionalFields = $providerObject->getAdditionalFields($taskInfo, null, $this);

SystemStatusUpdateTaskNotificationEmailField gets called with a null task, but it unconditionally calls $task->getNotificationEmail().


Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Bug #62274: Regression: Unable to create scheduler-tasksClosed2014-10-16

Actions
Related to TYPO3 Core - Bug #55760: Unable to create scheduler-tasksClosed2014-02-07

Actions
Related to TYPO3 Core - Bug #48022: Fatal error: Call to a member function getNotificationEmail() on a non-object when saving taskClosedThorsten Kahler2013-05-07

Actions
Actions #1

Updated by Christian Weiske over 7 years ago

Strangely on a 7.6.10 system that works, $schedulerModule->CMD is set to add, while it is set to edit on the broken system.

Actions #2

Updated by Christian Weiske over 7 years ago

Aha!

The scheduler extension was enabled recently, but the scheduler database tables did not exist.

Creating them with the install tool -> "compare database with specification" made it work.


Nontheless, the error message is very confusing.

Actions #3

Updated by Stephan Großberndt over 6 years ago

  • Assignee set to Stephan Großberndt

The problem is actually in the implementations of AdditionalFieldProviderInterface. Although even in PHPDoc its clearly stated * @param \TYPO3\CMS\Scheduler\Task\AbstractTask $task The task object being edited. Null when adding a task! some core additional fields do not check for NULL

Actions #4

Updated by Stephan Großberndt over 6 years ago

Ok, so since this happens when editing a task (editTaskAction) - task should not be NULL, so we might add a check on task being NULL when editing

Actions #5

Updated by Gerrit Code Review over 6 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/55122

Actions #6

Updated by Gerrit Code Review over 6 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/55122

Actions #7

Updated by Stephan Großberndt over 6 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #8

Updated by Gerrit Code Review over 6 years ago

  • Status changed from Resolved to Under Review

Patch set 1 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/55267

Actions #9

Updated by Stephan Großberndt over 6 years ago

  • Status changed from Under Review to Resolved
Actions #10

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF