19094 pointsCommunity rank #1Supreme DeityWPMU DEV StaffLifetime member
Support Chimp
(joined March 2010)
Likes (0)
On thing to keep in mind which I didn't mention was that if a post was scheduled to go live at 1pm and the next cron was 1329 then it won't get processed until then unless it got done by the previous cron.
Responses (2)
Support Chimp (joined March 2010) Likes (0)
Hey Basem.
Do you get a lot of spam as well?
To cut down on the load you could disable WP-Cron and then manually run it at server level:
This goes into your wp-config.php
define('DISABLE_WP_CRON', true);Do you use cPanel?
You can create crons in cPanel really easily.
If not and you are not sure then you could get your host to help you here, but something like this should work:
30 * * * wget -q -O - http://domain.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1The "*/30 * * *" sends the cron every 3 minutes.
The "> /dev/null 2>&1" ensures no emails are sent out.
There is a plugin for this, although I'd rather do it the way I mentioned above:
http://wordpress.org/extend/plugins/wp-cron-control/
Hope this helps :-)
Support Chimp (joined March 2010) Likes (0)
On thing to keep in mind which I didn't mention was that if a post was scheduled to go live at 1pm and the next cron was 1329 then it won't get processed until then unless it got done by the previous cron.
WordPress Questions?
We've got answers!
Find out more »