Every minute of every day of every week of every month, that command runs. man 5 crontab has the documentation of this. If you just type man crontab, you get the documentation for the crontab command. What you want is section 5 of the manual pages which covers system configuration files including the /etc/crontab file. … Read more
0 0,4,8,12,16,20 * * * /cmd.sh That’s probably how I would do it. This will run the job every 4 hours, on the hours of 00:00, 04:00, 08:00 12:00, 16:00, 20:00. This is just a little more verbose way of writing */4, but it should work the same.
I always found that logging cron job execution to a file is very helpful. Otherwise you have no idea if it’s working right. Just have your code open a file, write a timestamp, and close. Something simple like: $logfile = $_SERVER[‘DOCUMENT_ROOT’].’/CRON.txt’; $handle = fopen($logfile , ‘a’) or die(‘Cannot open file: ‘.$logfile ); $data=”cron task called … Read more
wget was fine. The client’s theme had a coming soon feature that was keeping the cron from processing.
Use WordPress Transient API instead. This should be something like this (modified your existing shortcode function). function skips_get_random_tags() { $transient_name=”skips_random_tag”; $transient_expiration = 60 * 60 * 24; // 1 day if ( false === ( $tag = get_transient( $transient_name ) ) ) { // tag isn’t found in transient so get it from WP database … Read more
I think your problem may be in the use of $post->ID. In your code $post is an undefined variable. As you are inside a loop, try get_the_ID() instead of $post->ID: $post_ID = get_the_ID(); $request_start_time = get_post_meta( $post_ID, ‘_simple_start_date’, true ); if (date(‘Ymd’) == date(‘Ymd’, $request_start_time)){ $current_user = $post->post_author; $request_date = get_post_meta( $post_ID, ‘_simple_start_date’,true ); $request_year … Read more
An asterisk in the minute (first) field tells it to run every minute, regardless of the other fields. You need to specify an exact minute to run within the hour. Be that on the hour (0), half past (30), etc.. 0 */2 * * * /path-to-script
Whenever I change the time intervals for ex: from ‘three_days’ to ‘five_minutes’ or from ‘five_minutes’ to ‘fifteen_minutes’, the cron is running with earlier frequency and not the updated one. Because you only reschedule the event if it does not exist: if ( ! wp_next_scheduled( ‘bd_cron_cache’ ) ) { // schedule } …which will always be … Read more
crontab -e then comment out each line you don’t want to run with #.
Cron fires outside of the standard WordPress loop, so $post will not be filled with any post-related data when the function is called. It should be obvious, then, that providing an ID directly isn’t referencing the non-existent $post variable which is why it works in that scenario. The best way to set post_statuses to expired … Read more