WP-CRON has its problems, and so long ago we decided to use crontab to trigger the WP-CRON system, and recently switched to WP CLI through crontab. Every once in a while, I’m seeing a fatal error in the database, and through debugging found that it’s coming from a scheduled cron named “wp\_privacy\_delete\_old\_export\_files”. The problem is that it has null args.
Of the couple of cron related plugins I looked at, both of them protect the WP core crons, and won’t let me delete “wp\_privacy\_delete\_old\_export\_files”. Since crons are just serialized data in the options table, I think I could easily modify that serialized data to remove the crons I want to remove. I’m just wondering if anyone thinks that’s a bad idea, and if so why.
For instance, there are some crons scheduled for 4+ years ago. They’re clearly never going to run successfully. Why shouldn’t I just delete them?
[ad_2]