Feature #4387

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

Added by Ingo Renner about 10 years ago. Updated 9 months ago.

Should have
Target version:
Start date:
Due date:
% Done:


PHP Version:
Sprint Focus:


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).


#1 Updated by Francois Suter about 10 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.

#2 Updated by Georg Ringer about 10 years ago

maybe using the update wizard?

#3 Updated by Francois Suter about 10 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.

#4 Updated by Ingo Renner about 10 years ago

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

#5 Updated by Michael Stucki almost 6 years ago

  • Category set to scheduler

#6 Updated by Michael Stucki almost 6 years ago

  • Project changed from Scheduler to TYPO3 Core
  • Category changed from scheduler to scheduler

#7 Updated by Mathias Schreiber almost 5 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" :)

#8 Updated by Alexander Opitz over 4 years ago

  • Status changed from Needs Feedback to New

Yes Mathias, that sounds correct.

#9 Updated by Daniel Goerz over 4 years ago

  • Parent task set to #68681

#10 Updated by Ingo Renner over 4 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.

#11 Updated by Jan Helke about 2 years ago

  • Assignee deleted (Mathias Schreiber)

#12 Updated by Susanne Moog 9 months ago

  • Parent task deleted (#68681)

Also available in: Atom PDF