Lack of interest Always run jobs as guest

This suggestion has been closed automatically because it did not receive enough votes over an extended period of time. If you wish to see this, please search for an open suggestion and, if you don't find any, post a new one.
This suggestion has been closed. Votes are no longer accepted.
Jobs (via job.php) are run as a guest -- we don't start the session, so the visitor won't be set via that, thus defaulting to a guest. Admittedly, manual runs via the ACP may be a little different, but that's not related to the example error.

Indeed, that error message is actually indicative that it is run as a guest. If it were run as a real user, there would be a valid user name. (You can also see the "unknown account" reference in the error log.)
 
Admittedly, manual runs via the ACP may be a little different, but that's not related to the example error.
That's exactly the point of the suggestion ;)

If you manually execute a cronjob from the backend, the environment is different so bugs like the one linked above might go unnoticed.

Therefore I'd appreciate if jobs would always (no mattter if triggered manually or automatically) be executed as a guest.
 
Top Bottom