Project

General

Profile

Actions

Feature #4387

closed

Provide a way to automatically install / set up a task upon installation of an extension

Added by Ingo Renner over 14 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
scheduler
Target version:
-
Start date:
2009-08-28
Due date:
% Done:

0%

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

Description

It'd be useful to have a way to automatically set up a task when installing an extension.

For example in the Solr extension I have a task that optimizes the Solr search index. Now it'd be nice to have such a task set up when installing that extension.
That'd also be useful for tasks that ship with the core (once we do that).


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #64093: Data Provider for scheduler tasksClosed2015-01-03

Actions
Related to TYPO3 Core - Feature #83338: Move scheduler tasks from serialized data to JSONClosed2017-12-15

Actions
Actions #1

Updated by Francois Suter over 14 years ago

That of course would be very nice, but I don't see how this could be done with the current structure of the EM.

Actions #2

Updated by Georg Ringer over 14 years ago

maybe using the update wizard?

Actions #3

Updated by Francois Suter over 14 years ago

That's a possibility, yes. What I don't like with the EM's update mechanism is that it cannot be launched automatically. Maybe it could be achieved by (mis-)using user-defined configuration options.

Actions #4

Updated by Ingo Renner over 14 years ago

abusing any of these systems is not an option. I'll work on something to achieve this for 4.4 I guess.

Actions #5

Updated by Michael Stucki over 10 years ago

  • Category set to scheduler
Actions #6

Updated by Michael Stucki over 10 years ago

  • Project changed from 739 to TYPO3 Core
  • Category changed from scheduler to scheduler
Actions #7

Updated by Mathias Schreiber about 9 years ago

  • Status changed from New to Needs Feedback
  • Assignee set to Mathias Schreiber

The task should be added but marked as disabled, right?
I just imagined extension author going like "yes, of course run [expensive action X] every minute" :)

Actions #8

Updated by Alexander Opitz almost 9 years ago

  • Status changed from Needs Feedback to New

Yes Mathias, that sounds correct.

Actions #9

Updated by Daniel Goerz over 8 years ago

  • Parent task set to #68681
Actions #10

Updated by Ingo Renner over 8 years ago

If the task can only be added as disabled then there's no point in having it really. After all you want to do certain things periodically for a reason. Yes, of course someone could do stupid things with it, but there are enough ways to do that otherwise as well. Let's try to trust people first.

An alternative would be to have a popup during installation similar to those dialogs you find with OAuth... Application FooBar would like to do A, B, and C. Which of these things do you want to allow? (All checked by default). This would be super user friendly. Something would need to get figured out for non-backend EM installations.

Actions #11

Updated by Jan Helke over 6 years ago

  • Assignee deleted (Mathias Schreiber)
Actions #12

Updated by Susanne Moog about 5 years ago

  • Parent task deleted (#68681)
Actions #13

Updated by Georg Ringer about 4 years ago

Actions #14

Updated by Georg Ringer about 4 years ago

  • Related to Feature #83338: Move scheduler tasks from serialized data to JSON added
Actions #15

Updated by Anonymous over 3 years ago

Maybe it would also be possible to add another section to the Scheduler Module called "Suggestions" where extensions could suggest crons with interval, arguments etc. so you would just have to click a "+" Icon in the end to add this specific task with the suggested settings. Also there should be a second button like "Add and Modify" which opens an edit view for the task prefilled but let's the user change settings before adding the task.

Just giving extensions the possibility to add active scheduler tasks would open up doors for nasty conflicts between extensions I think. Also certain extensions could be used for multiple purposes and an extension author might only have one of multiple purposes in mind.

Actions #16

Updated by Christian Kuhn about 2 years ago

  • Status changed from New to Closed

Hey. I hope it's ok to close this issue for now: The scheduler needs a revamp and should be free'd from both the 'serialize' issue and probably the db-based setup in general. I think we'll pick this issue up again when we continue to work on the scheduler in general, and will then do that with fresh issues.

Actions

Also available in: Atom PDF