Commit 2892f6dc authored by Michael Oehlhof's avatar Michael Oehlhof Committed by Markus Klein
Browse files

[TASK] EXT:Scheduler: Update documentation

Replaced images with new ones from current master.
Adjust the description text where necessary.
Change presentation of the "class not found" group.

Resolves: #72628
Releases: master
Change-Id: Icf6845c72b34afbf0105aa844e321a18878f16dd

Reviewed-by: Christian Kuhn's avatarChristian Kuhn <>
Tested-by: Christian Kuhn's avatarChristian Kuhn <>
Tested-by: default avatarTYPO3com <>
Reviewed-by: Markus Klein's avatarMarkus Klein <>
Tested-by: Markus Klein's avatarMarkus Klein <>
parent 14bf99b2
.. ==================================================
.. --------------------------------------------------
.. -*- coding: utf-8 -*- with BOM.
.. include:: ../../Includes.txt
.. _scheduler-user:
The Scheduler user
When tasks are launched manually from the BE module, they are executed
using the current BE user. When tasks are run from the command line,
however, a specific command-line user, called "\_cli\_" with admin rights
is created on-the-fly.
\ No newline at end of file
......@@ -20,12 +20,12 @@ installation. It will probably look something like this:
Checking the setup of the Scheduler
The first warning just means that the Scheduler has never run
yet and can be safely ignored for now. The second message is an error
and must be addressed. See next section.
The first message shows a warning that the Scheduler has never run
yet or an information about the last run.
The third message should normally be okay. If there's an error
The second message should normally be okay. If there's an error
instead, it means that permissions to execute TYPO3's command-line
dispatcher must be checked (this is not strictly related to the
The third message shows information about the current server time.
......@@ -75,7 +75,7 @@ Follow-up
Whenever a task starts or ends a message is written to TYPO'3 system
log (viewable in the Admin Tools > Log module). A message is also
log (viewable in SYSTEM > Log). A message is also
written when a parallel execution has been blocked. This makes it
possible to follow what happens, since the main purpose of the
Scheduler is to run things when nobody is watching.
......@@ -271,7 +271,7 @@
<source>Please select at least one cache backend.</source>
<trans-unit id="msg.invalidTaskClass">
<source>Class %s of the registered task could not be found. You should re-install the extension that provided it or simply delete this task.</source>
<source>The class of a registered task could not be found. You should re-install the extension that provided it or simply delete this task.</source>
<trans-unit id="msg.invalidTaskClassEdit">
<source>The current class (%s) could not be found. Change it below or consider deleting this task altogether.</source>
......@@ -79,7 +79,7 @@
<td><span class="t-span">{taskRecord.frequency}</span></td>
<td><span class="t-span">{taskRecord.multiple}</span></td>
<td><span class="t-span">{taskRecord.lastExecution}</span></td>
<td><span class="t-span">{taskRecord.nextDate}</span></td>
<td><span class="t-span {taskRecord.labels.nextexecution.class}">{taskRecord.nextDate}</span></td>
<td class="nowrap"><span class="t-span">
<f:if condition="{taskRecord.isRunning}">
......@@ -139,6 +139,12 @@
<f:if condition="{missingClasses}">
<table class="table table-striped table-hover" style="margin-bottom: -2px;">
<tr class="taskGroup" data-task-group-id="0">
<td><span><strong><f:translate key="msg.invalidTaskClass" /></strong></span>
<table class="table table-striped table-hover">
<th><span class="t-span"><f:translate key="" /></span></th>
......@@ -148,7 +154,7 @@
<f:for each="{missingClasses}" as="missingClass">
<td class="right">{missingClass.uid}</td>
<td><span class="label label-danger" style="white-space: normal"><f:translate key="msg.invalidTaskClass" arguments="{0: '{missingClass.class}'}" /></span></td>
<td><span class="label label-danger">{missingClass.class}</span></td>
<td class="nowrap">
<div class="btn-group" role="group">
<a data-toggle="tooltip" data-container="body" class="btn btn-default t3js-modal-trigger" href="{moduleUri}&CMD=delete&tx_scheduler[uid]={missingClass.uid}"
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment