you could use something like this, WP Crontrol to see what those events might be and when they are scheduled to run ( interval ), but the time of the day ( when they run ) is controlled by visitors viewing your site ( which is why they run during the day, because that when … Read more
Welcome to the forum! By default, wp-cron runs every time an HTTP request is made to a WordPress site. For this reason, really popular websites have found it necessary to disable the default wp-cron functionality and replace it with a real cron job. There are several articles available on how to do this. Using the … Read more
Question: Will each instance try to run the same job Yes! If you have 5 machines running the same site, they’ll all try to run the cron job. It’ll be inconsistent, but if machine 1 triggers WP Cron and there’s an event ready to run, and machine 2 triggers WP Cron, then machine 2 will … Read more
If your site is using HTTP Authentication (you know, the dialog/prompt that pops up and asks for your username and password), WP Cron will not work. This is because WP Cron does not present the proper login credentials when making the request. To help with this, there is a free plugin that enables WP Cron … Read more
WP CLI to the rescue! Instead of using php and trying to figure out the rest, install it on the server and just have your cron execute wp cron event run –due-now –path=/home/mysite_staging/www/example.com/
Ok, things are working now. Not sure if it was fact that cron environment didn’t have its PATH set as needed, or if there was other reason, but I followed the instructions here: https://peterwilson.cc/real-wordpress-cron-with-wp-cli/ and https://purpleturtlecreative.com/blog/2020/02/how-to-replace-the-wordpress-cron-with-a-linux-cron-job/ So now, my crontab is PATH=/usr/local/opt/[email protected]/bin:/usr/local/opt/[email protected]/bin:/usr/local/opt/[email protected]/sbin:/usr/local/opt/[email protected]/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin * * * * * /bin/bash /folder/wordpresscron.sh (with newline after the crontab entry) … Read more
No, not quite. When you say this: wp_schedule_single_event( $sent_on, ‘my_custom_cron’, [ $notif_id, $notif_name, $membership_id, $lesson_id ] ); You are essentially saying is when the current time passes $sent_on, do: do_action( ‘my_custom_cron’, [ $notif_id, $notif_name, $membership_id, $lesson_id ] ); Cron jobs are just a TODO note to fire an action with some arguments in the future. … Read more
strtotime( ‘midnight’ ) will give you midnight for today, which has already happened! You want midnight for tomorrow. e.g. date( ‘F jS H:i:s’, strtotime( ‘midnight’ ) ) on July 19th is July 19th 00:00:00 However, date( ‘F jS H:i:s’, strtotime( ‘tomorrow midnight’ ) ) would be July 20th 00:00:00 …which is what you want! So … Read more
add_action(‘opbs_update_counts’, array(‘cronTaskUpdateCounts’)); should be add_action( ‘opbs_update_counts’, array( $this, ‘cronTaskUpdateCounts’ ) );
You need to schedule the event differently. In your approach, you hook to wp to schedule the event, meaning that it is called everytime WordPress is called, setting your option back. I am not quite sure if the schedule is postponed or if you create multiple schedules this way, but it is not correct. You … Read more