Make WordPress Core

Changes between Version 1 and Version 2 of Ticket #57924, comment 10


Ignore:
Timestamp:
03/16/2023 03:45:32 PM (3 years ago)
Author:
j3gaming
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #57924, comment 10

    v1 v2  
    2626> Whilst this is an irritating problem when it happens sporadically on sites (as with the `could_not_set` issue) the missing schedule is picked up quickly and added again; when ''your'' cron jobs are set to run **every** minute and your database backup (which locks the database) runs for several minutes, it's going to be much more prevalent and 100% likely to occur and 100% likely that schedules are not added as required.
    2727
    28 Yes, it looks like I need to have the crons added via code. That way if they are ever missing from the crons option, they are immediately re-added. I think this type of code has been covering up this problem for a long time. Using a plug-in to add/remove crons (like WP Control) is the only way to experience them being deleted.
     28Yes, it looks like I need to have the crons added via code. That way if they are ever missing from the crons option, they are immediately re-added. I think this type of code has been covering up this problem for a long time. Using a plug-in to add/remove crons (like WP Control), or anything that only one-off adds the cron, is the only way to experience them being deleted.
    2929
    3030Can you do a test for me? Install WP Control and add a cron to it. Next time you get a could_not_set, can you see if it's still there?