Although both of your options (that is, using transients or using a cron job) are viable, I’m a fan of using transients unless the dataset is exceptionally large or if there is some need to automate the process. Without seeing much of your current code, it’s difficult to give a working example. Nonetheless, if you … Read more
The Problem: When wp-cron.php is called, it includes only: require_once( dirname( __FILE__ ) . ‘/wp-load.php’ ); so the problem you are facing is that wpmu_delete_blog() is undefined when you call it from your remove_blogs_daily() function. Possible Solution: You therefore need to add this line: require_once( ABSPATH . ‘wp-admin/includes/admin.php’ ); into your code to fix that. … Read more
When you run things on the CLI (which is pretty much where Cronjob and runwhen jobs are running), then you don’t have access to some things like some server or request variable contents, etc. What you need to do is fire up WP Core. Else you won’t have access to the full WP API. One … Read more
If you want a quick programmatic way of looping through everything you have in the cron row inside wp_options and you have access to the site’s database directly (either in a local development environment or on a webhost), you can run something like this via the command line: mysql $YOUR_DB_NAME -e “SELECT option_value FROM wp_options … Read more
When you register a scheduled event for WordPress’ cron, the 3rd argument is a hook name: wp_schedule_event( time(), ‘hourly’, ‘my_hourly_event’ ); And you add a function to run on this hook with add_action(): add_action( ‘my_hourly_event’, ‘do_this_hourly’ ); This will cause do_this_hourly() to run whenever the scheduled event runs. This works because when the scheduled time … Read more
Since wp_mail is pluggable, we can selectively override it. I run the following code in my general functionality plugin: /** * Email Async. * * We override the wp_mail function for all non-cron requests with a function that simply * captures the arguments and schedules a cron event to send the email. */ if ( … Read more
wp_cron operates on intervals and there is no interval that will hit exactly the first day and the 15th of every month. You could run your wp-cron job every day and check the date, similar to this but with a simple callback like: cron_callback_wpse_113675() { $date = date(‘d’); if (’01’ == $date || ’15’ == … Read more
I actually found out that the Cron works, just not as I expected. I refreshed the pages and called wp-cron.php (using wget) a couple of times, and I kept seeing my cron task schedule with “-X seconds“. Then I stopped for a minute or two, and refreshed the frontend page of the site, and my … Read more
It seems to have solved by changing the two functions, by taking a different approach: /* CHECK IF CURRENT USER IS NOT IN POST.PHP AND IN POST-NEW.PHP AND DOWNGRADE PUBLISH POSTS IN PENDING AFTER X DAYS */ if(is_admin() ) {global $pagenow; if( ‘post.php’ != $pagenow || ‘post-new.php’ != $pagenow) { add_action( ‘init’, ‘downgrade_publish_posts’ ); function … Read more
Xaedes solution in https://wordpress.stackexchange.com/a/76466/107596 works quite well: <?php if( php_sapi_name() !== ‘cli’ ) { die(“Meant to be run from command line”); } function find_wordpress_base_path() { $dir = dirname(__FILE__); do { //it is possible to check for other files here if( file_exists($dir.”/wp-config.php”) ) { return $dir; } } while( $dir = realpath(“$dir/..”) ); return null; } … Read more