en	Add task

en	Edit task

en	Cancel

en	Scheduled tasks

en	Setup check

en	Information

en	CLI script

en	Last run

en	TYPO3 Scheduler backend user

en	automatically

en	Backend types

en	Number of days until removing files

en	Check/uncheck all

en	Class

en	Cron

en	Definition type

en	Interval

en	Cron command

en	Description

en	Email

en	End (HH:MM DD-MM-YYYY)

en	Execute selected tasks

en	Extension

en	Frequency

en	Frequency (seconds or cron command)

en	ID

en	Last Execution

en	Manual

en	manually

en	Name

en	Next Execution

en	Parallel Execution

en	Allow Parallel Execution

en	Server time

en	Sleep time

en	Start (HH:MM DD-MM-YYYY)

en	Storage to index

en	Number of files per run

en	Clean all available tables

en	Table to clean up

en	Table: %s

en	All tables

en	Delete entries older than given number of days

en	Type

en	Recurring

en	Single

en	Task group

en	The task could not be added.

en	The task was added successfully.

en	The script to execute the Scheduler from the command line is: <strong>"%s scheduler"</strong>.

en	The webserver user is allowed execute this script.

en	The webserver user is not allowed to execute this script.

en	Are you sure you want to delete this task?

en	The task could not be deleted.

en	The task was successfully deleted.

en	The end date is before the start date.

en	Executed: %s

en	Invalid frequency. Please enter either a number of seconds or a valid cron command. The cron parser said: %1$s [code: %2$d].

en	The information about the last execution of the Scheduler is incomplete.

en	This is the list of all available tasks in this TYPO3 installation. Click on the icon at the far right to directly create a new scheduled task of the chosen type.

en	Invalid frequency. Please enter either a number of seconds or a valid cron command.

en	Please enter a sleep time greater or equal to 0 (zero).

en	The Scheduler was last started (%1$s) on %2$s at %3$s and ended on %4$s at %5$s.

en	A running task may not be deleted.

en	A running task may not be edited.

en	The task is not running. There are no executions to unmark.

en	Please enter an email address.

en	No frequency was defined, either as an interval or as a cron command.

en	The Scheduler has never yet run or the information about the last run has been lost.

en	There are currently no task classes available at all. To be able to create new tasks, you must either enable the samples provided by the Scheduler or install some other extension that relies on the Scheduler.

en	The selected task class could not be found. You should probably contact the task's developers.

en	No tasks defined yet.

en	Not executed: %s

en	Execution of task "%1$s" failed with the following message: %2$s

en	The execution failed, but the error message could not be retrieved (it was probably too large). Sorry.

en	Execution failed: %1$d, %2$s

en	Please define a start date.

en	Start date is invalid.

en	End date is invalid.

en	Number of days is invalid.

en	Some of the selected cache backends do not exist. Please select valid backends only.

en	Please select at least one cache backend.

en	Class %s of the registered task could not be found. You should re-install the extension that provided it or simply delete this task.

en	The current class (%s) could not be found. Change it below or consider deleting this task altogether.

en	This screen checks if the requisites for running the Scheduler as a cron job are fulfilled. It also displays information about the last run of the Scheduler.

en	The backend user "_cli_scheduler" is used by the CLI-script to log into TYPO3. This user may not have administrator privileges. The user's password is not important but should be set to a secure value for security reasons.

en	The backend user "_cli_scheduler" was found.

en	The backend user "_cli_scheduler" exists but is currently disabled.

en	The backend user "_cli_scheduler" was not found. <a href="%s" title="Click to create the missing user">Create the user now</a>.

en	Current server time is %s.

en	All dates and times in the Scheduler are measured according to the server's time, as the Scheduler is run purely on the server-side.

en	Are you sure you want to mark this task as not running? Note that this will not stop the actual script (if unsure please refer to the manual).

en	The task could not be marked as non-running.

en	The task was successfully marked as non-running.

en	The requested task (UID: %d) was not found.

en	The task was updated successfully.

en	The task could not be updated.

en	The "_cli_scheduler" user was created successfully.

en	The "_cli_scheduler" user already exists. It was not created.

en	The creation of the "_cli_scheduler" user failed.

en	None

en	Status

en	Progress

en	Status Legend

en	Disabled, will not be executed, except manually

en	Failure! An error occurred during the last execution (move over bullet for more details)

en	Late, will run with next execution

en	Currently running

en	Scheduled, will run on next possible execution

en	disabled

en	failure

en	late

en	running

en	scheduled

en	Task

en	TYPO3 Scheduler administration module

en	Run task

en	Scheduler test task

en	The Scheduler test task just sends a mail to a given email address. It is designed to be used for testing purposes.

en	Scheduler sleep task

en	This task does nothing but put PHP to sleep for a number of seconds. It is designed to test multiple executions.

en	Caching framework garbage collection

en	This task calls the garbage collection of configured caching framework caches which use one of the selected backends. This will free some space in cache backends which do not have an internal garbage collection. In case of the default database backend it is advisable to run this task once a day when the database is mostly idle.

en	[OBSOLETE] File Abstraction Layer: Indexing job

en	Runs indexing tasks based on an indexing configuration and a storage/folder information.

en	File Abstraction Layer: Update storage index

en	Updates the Index/Cache Data of a Storage; only needed if changes to the storage are possible outside the backend (FTP, RemoteStorages).

en	File Abstraction Layer: Extract metadata in storage

en	Extracts metadata for all files in storage which have been changed since last run.

en	Table garbage collection

en	Task to delete old entries from specific tables like sys_log. Use $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['scheduler']['tasks']['tx_scheduler_TableGarbageCollection']['options']['tables'] to configure tables. Refer to the manual for more details.

en	Fileadmin garbage collection

en	This task empties all "_recycler_" folders below fileadmin. This helps free some space in the file system.