Where are you putting the wp_schedule_event() code? My guess is, you have it somewhere that’s causing it to run on every page load, causing the action to be scheduled multiple times (like maybe you just dropped it in your functions.php?). You only need to schedule the action once. The easiest way is to do it … Read more
You can do this via wp_cron by using the following, function more_reccurences() { return array( ‘sixhourly’ => array(‘interval’ => 21600, ‘display’ => ‘Every 6 hours’), ); } add_filter(‘cron_schedules’, ‘more_reccurences’); then find the function that does the autopost and call it by if ( !wp_next_scheduled(‘autopost_function’) ) { wp_schedule_event(time(), ‘sixhourly’, ‘autopost_function’); } If you want to use … Read more
add_action( ‘wp’, ‘delete_expired_coupons_daily’ ); function delete_expired_coupons_daily() { if ( ! wp_next_scheduled( ‘delete_expired_coupons’ ) ) { wp_schedule_event( time(), ‘daily’, ‘delete_expired_coupons’); } } add_action( ‘delete_expired_coupons’, ‘delete_expired_coupons_callback’ ); function delete_expired_coupons_callback() { $args = array( ‘post_type’ => ‘coupon’, ‘posts_per_page’ => -1 ); $coupons = new WP_Query($args); if ($coupons->have_posts()): while($coupons->have_posts()): $coupons->the_post(); // get the post publish date $test = get_the_date(); … Read more
First of all you have to remember how WP cron works. The action will trigger when someone visits your WordPress site, if the scheduled time has passed. So if your site isn’t very crowded at 3am, the cron job won’t start exactly at 3am. (You should use real cron if you really need to run … Read more
Removing / un-scheduling obsolete cron jobs can be achieved using this code snippet. add_action(“init”, “remove_cron_job”); function remove_cron_job() { wp_clear_scheduled_hook(“my_schedule_hook”); } Change the my_schedule_hook to cron’s hook name and add the code in your theme’s function.php file.
In your code you have: if ( isset( $_POST[“run_import”] ) ) { add_action( ‘import_execution_event_test’, … But when wp-cron.php is spawned, there’s probably no POST variable called run_import, so your action is never added, and thus not triggered.
Unfortunately, you cannot run script on every 12 December. WP Cron can be only defined as interval from first execution of script, so you have to execute script on 12 December with one year interval to do exactly what you want. I will suggest you to create WP Cron job with daily interval and check … Read more
Part 1. The Time != The Timestamp This is your problem: every midnight at Local Timestamp There is no such thing as a local timestamp. Timestamps are not timezoned, it’s not that WP uses UTC, but rather that UTC timestamps just happen to be +0 hours. If you want it to happen at midnight local … Read more
You have the wrong period alias in your code You added your personal period in my_cron_schedules() as 61sec: $schedules[“61sec”] = array( but use it in setup_schedule() as 61sek: wp_schedule_event( current_time(‘timestamp’), ’61sek’ , ‘expire_ogl’); The other parts of the code look right.
If you don’t have control over the API, you’re doing it almost right. That is what cron jobs are for. What needs to be avoided is possible overlapping API calls that do the same thing. Why not instead have a meta field automation_operation_status that stores the … status? Like pending, running, complete, error. Then, in … Read more