Project

General

Profile

Actions

Feature #25338

closed

Provide maintenance scheduler tasks

Added by Xavier Perseguers about 13 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-03-16
Due date:
% Done:

0%

Estimated time:
PHP Version:
5.2
Tags:
Complexity:
Sprint Focus:

Description

This bug entry serves as an umbrella for scheduler tasks that should be provided by TYPO3 itself to be set up and used by administrators.

(issue imported from #M17965)


Related issues 4 (0 open4 closed)

Related to TYPO3 Core - Feature #25339: Create scheduler task for lowlevel_refindexClosed2011-03-16

Actions
Related to TYPO3 Core - Feature #25341: Create scheduler task to reclaim spaces and optimize tablesClosedMorton Jonuschat2011-03-16

Actions
Related to TYPO3 Core - Feature #25342: Create scheduler task to empty recycler folders within fileadmin/Closed2011-03-16

Actions
Related to TYPO3 Core - Feature #25343: Scheduler task to delete old rows from database tablesClosed2011-03-16

Actions
Actions #1

Updated by Christian Kuhn almost 13 years ago

There has been a discussion in the pending child issues about 'umbrella' tasks that solve more than one problem at once.

Here are some of the tasks we currently have, or which we can / should have in the future:

- A task to delete old files in recycler directories within fileadmin/ (issue #25342)
- A task to delete 'old' typo3temp files
- A task to clean 'always growing' tables like sys_log or sys_history (issue #25343)
- A task to execute the caching framework garbage collection (exists already)
- A task to update refindex (exists as cli)
- ...

There are different opinions on how those tasks could be combined:
- Some people want to combine all file related tasks (eg. recycler task and typo3temp/ task) in only one task. But I think deleting unused typo3temp files and cleaning recycler folders are imho two different things for two special different purposes, thus they should be supplied as single tasks.
- People want to clear different tables which accumulate data over time (eg. sys_log and sys_history). This is imho easily possible, but for admin security the 'cleanable' tables should be preconfigured, but they can be combined in one task (will do with issue #25343)
- Other tasks like a refindex updater, a flexform cleaner or a caching framework garbage collection still solve different things and should be implemented as stand alone tasks.

I think, we should not create a 'magic cleaner task' that calls all arbitrary and different cleanup things at once. I'd instead vote to deliver a (dummy, introduction) package that pre-configures all those tasks with sane defaults (eg: The typo3temp/ task runs once a month, the TER update task runs daily, the fileadmin recycler task and sys_log cleanup task runs weekly). We could also deliver an update wizard that registers those tasks with sane defaults during update. That is imho the direction we should go: Deliver single tasks for special purposes, but pre-configure them with sane defaults if an admin chooses to do so).

Actions #2

Updated by Xavier Perseguers over 12 years ago

  • Target version deleted (4.6.0-beta1)
Actions #3

Updated by Mathias Schreiber about 9 years ago

  • Status changed from New to Closed

I put the related tickets into the queue, freeing up this ticket.

Actions

Also available in: Atom PDF