You know what really pisses me off sometimes? WordPress. Never use the schedule post feature – it’s a useless piece of shit. WordPress allows you to write a draft blog entry and then schedule it to publish at a later date. Every time I do this, it always misses the schedule and then I struggle severely to get it published because it keeps scheduling it. Well maybe I don’t want it scheduled you stupid bitch, I just want it live. I set my end of the decade ramble to publish at 8AM and was supposed to wake up with it here. Instead it’s being a shithead and now I can’t get it published. This also happens on another WordPress blog I maintain. Could be a server setting, but it’s poorly documented. Fix your shit.
Edit. Okay so I Googled this a little bit. Seems like what happens is that WordPress runs a cron (automation) job. There’s a setting in wp-includes/cron.php where it checks every .01 seconds, so if the server is a slow piece of crap and can’t keep up, it misses it. I set it to check less frequently and that might work.
Change:
$cron_url = get_option( 'siteurl' ) . '/wp-cron.php?doing_wp_cron';
wp_remote_post( $cron_url, array('timeout' => 0.01, 'blocking' => false, 'sslverify' => apply_filters('https_local_ssl_verify', true)) );
TO
$cron_url = get_option( 'siteurl' ) . '/wp-cron.php?doing_wp_cron';
wp_remote_post( $cron_url, array('timeout' => 20, 'blocking' => false, 'sslverify' => apply_filters('https_local_ssl_verify', true)) );
A post (the decade recap) is scheduled for 11:45AM EST. It better work.
WordPress
Come on, WordPress…
December 31, 2009
Rants, Website Related
No Comments
Portfolioso
You know what really pisses me off sometimes? WordPress. Never use the schedule post feature – it’s a useless piece of shit. WordPress allows you to write a draft blog entry and then schedule it to publish at a later date. Every time I do this, it always misses the schedule and then I struggle severely to get it published because it keeps scheduling it. Well maybe I don’t want it scheduled you stupid bitch, I just want it live. I set my end of the decade ramble to publish at 8AM and was supposed to wake up with it here. Instead it’s being a shithead and now I can’t get it published. This also happens on another WordPress blog I maintain. Could be a server setting, but it’s poorly documented. Fix your shit.
Edit. Okay so I Googled this a little bit. Seems like what happens is that WordPress runs a cron (automation) job. There’s a setting in wp-includes/cron.php where it checks every .01 seconds, so if the server is a slow piece of crap and can’t keep up, it misses it. I set it to check less frequently and that might work.
Change:
$cron_url = get_option( 'siteurl' ) . '/wp-cron.php?doing_wp_cron';wp_remote_post( $cron_url, array('timeout' => 0.01, 'blocking' => false, 'sslverify' => apply_filters('https_local_ssl_verify', true)) );
TO
$cron_url = get_option( 'siteurl' ) . '/wp-cron.php?doing_wp_cron';wp_remote_post( $cron_url, array('timeout' => 20, 'blocking' => false, 'sslverify' => apply_filters('https_local_ssl_verify', true)) );
A post (the decade recap) is scheduled for 11:45AM EST. It better work.
WordPress