A much cleaner solution is to just set the post status via pre_get_posts. By default, the main query only shows published posts to logged out users and published and private posts to logged in users. We can add future posts to main query with pre_get_posts add_action( ‘pre_get_posts’, function ( $q ) { if ( !is_admin() … Read more
Added the following to my theme’s functions.php: define(‘WPMS_DELAY’, 5); // Run the below cron task every X minutes define(‘WPMS_OPTION’, ‘wp_missed_schedule’); function wpms_replacements_deactivate() { delete_option(WPMS_OPTION); } register_deactivation_hook(__FILE__, ‘wpms_replacements_deactivate’); // Run the following code on every request function wpms_init() { remove_action(‘publish_future_post’, ‘check_and_publish_future_post’); $last = get_option(WPMS_OPTION, false); // Exit here if less than WPMS_DELAY minutes has passed since … Read more
If you made your special offers a custom post type you could set the ‘scheduled’ date to the day you wanted it to expire then use this code to auto publish it on schedule after you’ve changed the scheduled date. The ‘future_show’ line goes with my ‘show’ custom post type so if you had a … Read more
The plugin Automatic Post Date Filler suggested in the comments is a perfect solution. Even better than imagined with all the various preferences to how it dynamically sets up the defaults when you edit the scheduled time.
Due to your server configuration, you may need to use the alternate cron method, which uses redirect rather than http loopback. Try adding the following to your wp-config.php file: // Alternate cron method define( ‘ALTERNATE_WP_CRON’, true );
The short answer is, post_date and post_date_gmt will be set to the date you scheduled the post to be published – not the date you created the post -, so post_date and post_date_gmt are holding the publishing date. Update: As reply to comment: When will the wp_insert_post hook be triggered? Actually both times, so on … Read more
In short, you can make future posts visible by telling WordPress to mark them as ‘published’ instead of ‘scheduled’. You do this by using a future_post hook, which gets called when a post changes status. Each post type automatically gets its own future hook; since the custom post type I’m using is event, I can … Read more
The solution was to apt-get remove tzdata apt-get install tzdata while dpkg-reconfigure tzdata was not enough. Mark’s edit: In human words, the problem was caused because the time zone data on the server was incorrect, which probably had an impact how php calculates times. The solution was to forcefully update the data.
This is the intended use of the WP_CRON_LOCK_TIMEOUT constant. When WordPress is loaded, it checks to see if a cron job is running (if cron is locked). If cron is not locked, it will try to create a lock – if the lock timeout has not been reached, no lock can be acquired and cron … Read more
Answer couldn’t be simpler. As pointed out by Otto at the wp-hackers list, problem was me not setting post_date_gmt when using wp_update_post(). Final code looks like this: if ( $post_date < strtotime( “tomorrow” ) ) { $status=”publish”; $newpostdata[‘post_status’] = $status; $newpostdata[‘post_date’] = date( ‘Y-m-d H:i:s’, $post_date ); // Also pass ‘post_date_gmt’ so that WP plays … Read more