New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regressed: Scheduled reports should be sent automatically by webcron, when cron is not setup #4612
Comments
maybe this is also the reason why piwik auto update is not working? |
shouldn't it be possible to check in each installation if this is working fine via the TasksTimetable Plugin? => if there are only negative times to next scheduled task - so all cron jobs are in the past- no cron (standart nor webcron) is working if so this problem is also in my installation because - otherwise I should have never seen/found this problem |
if this influences also all standard task: delete, archive, optimize etc which could be seen in the TaskTimetable Plugin Prio and Version to fix should be set as high as /near as possible... what do you think? |
Since I check for piwik update on our testing site at least once per week to latest version/beta, one could calculate from the entries in TaskTimetable Pluging when / in which version the problem starts... please see attachement Scheduled Tasks The following tasks are scheduled to be executed based on the current server time Monday 3 February 2014 13:18:18. |
Attachment: |
thanks for the fix. Since there is no change in list of tasks visible within TaskTimetable Plugin: do we have to restart the webcron jobs with standard setting / standard tasks? |
It should be triggered at some point when visits are tracked. |
Attachment: |
sorry looks still the same - no new tasks :-( |
I think it's a different bug @hpvd. Do you mind opening new one with this particular case of "tasks scheduled in the past are not running as expected". |
…wser archiving is enabled. Also fixes lots of errors that happened when the actual tasks were executed. For instance Twig was not found, some DB methods were missing because TrackerDB is slightly different and so on. Therefore we reuse the CronArchive logic to trigger scheduled tasks via HTTP which makes sure they are executed the same way and not in a limited Tracker mode way
…ust want to run scheduled tasks
It used to work this way:
This seems to have regressed in 2.0 as we got several reports by users that this stopped working.
Let's investigate the webcron and fix. Hopefully we can add integration test for this feature?
The text was updated successfully, but these errors were encountered: