Project

General

Profile

Actions

Feature #27265

closed

Possibility for non-admin Users to stop/pause/skip execution of a crontask

Added by Markus Greulich almost 13 years ago. Updated over 10 years ago.

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

0%

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

Description

It would be great if there was a way for non-admin users to stop/pause/skip the execution of a crontask.
At the moment it seems only admin-users can edit the crontasks set up in scheduler.

Here's what the idea behind it is:
There's a Newsletter that's generated daily and sent.
Now as there are certain days (like regular holidays) where there's no new news the news-entering User
would have to stop/skip/pause the generating task so it doesn't generate an empty/useless newsletter.

This of course is just an example... there are more reasons for users to stop crontabs from executing for a limited time...

Best would be a list of dates the task is not started. - An easy Access to the enable/disable functionality
for non admins would be enough though...

Best regards,
Markus

Actions #1

Updated by Georg Ringer almost 13 years ago

IMO this is feature which is wrong at the 1st place. tasks are for admins and not for editors.

Some words about your example with the newsletter:
There is IMO no extension out there, which creates automatically newsletters and sends those. And if there is: why should this extension send empty newsletters? IMO the solution is to send the automatic newsletters if there is content for it.

If you really need those custom stop/start thing, just implement a very simple extension where users can edit a record which got a relation to crontasks and the info about start & stop. create a cron which runs over your records and disables the task records. IMO the requirements are such specific that it would be hard to implement that in the core to fit every need.

Actions #2

Updated by Markus Greulich almost 13 years ago

Okay, i can understand the objection that tasks are for admins only...

But still i think it could be usefull that editors can stop certain tasks... i mean the "deactiviate" switch is there anyways.. why not make it possible to make it accessible for editors - that could be an optional setting for each task for example...

As for the newsletter-extension - "direct mail" will have that feature in it's next release probably... it's already in the SVN and working good...

It's usefull to send a list of tt_news records (of the last 24 hours for example) but on holidays if there are no new articles it'll only send the "no items in this view" thingie...

Thanks for the idea of the extension to control the tasks indirectly...
i will think about that, but still an accessible switch for editors, IMO would be a good thing.

Actions #3

Updated by Francois Suter almost 13 years ago

Markus Greulich wrote:

Thanks for the idea of the extension to control the tasks indirectly...
i will think about that, but still an accessible switch for editors, IMO would be a good thing.

This could also be implemented specifically for an extension, as I don't see a global need for it. I made such an implementation in my "external_import" extension whose BE module (which is available in User Tools) provides a form for setting and unsetting the external_import Scheduler task.

http://typo3.org/extensions/repository/view/external_import/current/

Maybe this helps you. I've been thinking for a long time already that it would be nice if the Scheduler provided an API for this, as it would make it easy to have such forms inside other extensions, but I never had enough need to invest time into this ;-)

But on the principle, I fully agree with Georg, managing tasks is really an admin's job.

Actions #4

Updated by Dmitry Dulepov almost 13 years ago

I agree with Georg. That's extension's problem, not scheduler's.

Actions #5

Updated by Francois Suter almost 13 years ago

  • Status changed from New to Closed

According to the discussion, I'm closing this issue.

Markus, feel free to reopen it if you disagree ;-)

Actions #6

Updated by Michael Stucki over 10 years ago

  • Category set to scheduler
Actions #7

Updated by Michael Stucki over 10 years ago

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

Also available in: Atom PDF