Hello,
Thank you for reaching out.
Can you please try setting new job on the latest version and see how it goes with the scheduling?
Best Regards,
@saranshwpm Tested on a very small site. Didn’t work. When the scheduled time was passed, the next run time switched to “January 1, 1970 at 02:00 by WP-Cron”. Same behaviour as on 30 other sites …. 🙁
Hi,
Can you please make sure that date formatting are set correctly and synced between WordPress and BackWPUp. If it is set to custom, please try with default date format in WordPress settings.
Best Regards,
I’was having the same problem.
Backups got restarted every time cronjobs got executed because even a sucessfull backup didn’t update the next run date.
I tried to create a new backup-job with similar settings, no effect.
So I used crontrol, to check my cronjobs’ statuses and found out, that even calling mydomain.bla/wp-cron.php manually would not change their status. So I kept that Tab open, to reload and check the statuses afterwards while I was analyzing that problem.
I went on and deactivated non-vital plugins and found out that one of my plugins (APCu Manager) was causing this problem. I also tried to change the date-format before with no effect.
Changed everything back to what it was set before and reactivated APCu Manager. For now, it looks good. I have no explanation for the root cause of this.
Same problem here. No luck with deactivating/activating or recreating jobs. After the scheduled runtime it shows the 1970 timestamp.
PHP Fatal error: Uncaught Error: Unknown named parameter $arg in /web/wp/wp-includes/class-wp-hook.php:324
Stack trace:
#0 /web/wp/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters('', Array)
#1 /web/wp/wp-includes/plugin.php(565): WP_Hook->do_action(Array)
#2 /web/wp/wp-cron.php(191): do_action_ref_array('backwpup_cron', Array)
#3 {main}
thrown in /web/wp/wp-includes/class-wp-hook.php on line 324
Job runs when triggered manually.
Try deactivating all plugins except crontrol. Run the cronjob manually.
If crontrol now shows no belated plugins, one of your plugins is responsible.
Reactivate your other plugins in batches, to find the bad guy.
