[wp-trac] [WordPress Trac] #20537: Don't spawn cron requests for suspended blogs

[WordPress Trac]

#20537: Don't spawn cron requests for suspended blogs
--------------------------+-----------------------------
 Reporter:  ryan          |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Cron          |     Version:  3.3.1
 Severity:  normal        |  Resolution:
 Keywords:                |
--------------------------+-----------------------------

Old description:

> For multisite, spawning cron requests is wasteful and unnecessary.
> wp_cron()/spawn_cron()/wp-cron.php should check the blog's status and
> bail if the blog is suspended.

New description:

 {{{

 }}}
 For multisite, spawning cron requests is wasteful and unnecessary.
 wp_cron()/spawn_cron()/wp-cron.php should check the blog's status and bail
 if the blog is suspended.

--

Comment (by ryan):

 I can see it being good and bad, at least when considering core events. A
 hard freeze prevents future posts from accidentally getting published and
 pingbacks from accidentally going out from a blog that should be dead. The
 blog and the cron queue are frozen. Then again, there could be some events
 that should still be processed.  This was requested by some wp.com folks
 to shut up zombie blogs. How dead is dead enough?

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/20537#comment:3>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software