Apparently what I was looking for was a hook that sets “do_ping”, and grepping through the theme and plugins there was none. My guess is that it was set through either an old theme or plugin, and not unset when that was deleted. However, I did discover that this function will globally unset it regardless … Read more
The internal WordPress cron is dependent upon site visitors to fire, unlike linux or unix cron which is fired at specific times. Generally speaking, if you have regular and frequent visitors to your website WordPress cron will run your defined task. But if you don’t have that traffic WordPress doesn’t fire the events. If your … Read more
Cron jobs are simply PHP scripts that are controlled by time. If the PHP file is not executed, the cron job will not be executed either. Your option would be to set a cron job in your host’s control panel, to ping a page once in a while. You can ask your host’s support to … Read more
First, I would check the constant ‘DISABLE_WP_CRON’. If that constant is true, I would already warn the user. Then I would set a cron job with your plugin to update an option in the database. That option should be updated only by the cron job of your plugin. Then you can check if that option … Read more
You could just try the alternate WP Cron method, which doesn’t require loopbacks. Add define(‘ALTERNATE_WP_CRON’, true); to your wp-config.php file.
Inspect your Schedules The best way to learn coding is to turn debug on and simply inspect your output. If you want to dig deeper, then you often need a custom tool that allows you to inspect the result fast and nicely, readable formatted. I wrote a plugin for some other answer, that helps you … Read more
Unfortunately the WordPress cron jobs are only triggered when your site is visited This is true. The only way to reliably execute code (even if visitors don’t visit your site) is to use the unix cron functions. You can just setup a unix cron job that will do a wget on your homepage. Edit: You … Read more
You shouldn’t call wp_clear_scheduled_hook on every page load, because then you’re always restarting your wp-cron shcedule, with your current setup. Additionally this call: wp_clear_scheduled_hook( ‘le_do_this’ ); doesn’t make any difference, since le_do_this isn’t a hook name in your setup. You could try for example this test plugin: <?php /** * Plugin Name: Daily WP-Cron * … Read more
You’re missing one key component. Add this to your wp-config.php: define( ‘DISABLE_WP_CRON’, true ); Here are some other helpful constants for your wp-config.php: https://gist.github.com/MikeNGarrett/e20d77ca8ba4ae62adf5
With WP CLI I was able to avoid other plugins potentially interfering with publish_future post. Below is a perl fragment. On my host webdir is $HOME/public_html and bindir is /usr/bin. Note the use of –due-now. Only those hooks currently waiting to be fired will run. Also note you either need to cd into webdir or … Read more