TYPO3 Core

I would like to wait with this until the new Reports module is committed to the core. Indeed if the Reports module indeed makes it into 4.3, the check screen of the Scheduler will be remove and all messages from the Scheduler will go there.

But I'm not sure if the Reports module makes it possible to define actions inside the messages, so it's seems a bit of a shame to introduce that feature now if it is lost in a short while. Wait and see, but I opened an issue so as not to forget.

would it be better to use just one common "typo3 user" for background/underground tasks?

there is already the _cli_lowlevel and the _cli_crawler
are we sure we need also this _cli_scheduler ?

since they don't use "permissions", but have just to exist to allow _cli scripts to run...

if possible i would use _cli_lowlevel for everything-.

stefano

Hi,

would it be better to use just one common "typo3 user" for background/underground tasks?

there is already the _cli_lowlevel and the _cli_crawler
are we sure we need also this _cli_scheduler ?

since they don't use "permissions", but have just to exist to allow _cli scripts to run...

if possible i would use _cli_lowlevel for everything-.

I would need to check exactly how user authentication is made. Somehow the current way of registering CLI scripts kind of mixes up the module's name and the user name. So I'm not sure if it's really possible to change that user's name.

Anyway what would really be useful for the Scheduler, since it may run many different tasks, would be to be able to define a user per task. The Scheduler would then switch user for each task, somewhat like the simulate user feature admins can use in the BE. But that's too late to do that now. Maybe for 4.4.