[wp-trac] [WordPress Trac] #23133: Display a warning in the admin if cron tasks fail due to blocked HTTP requests

[WordPress Trac]

#23133: Display a warning in the admin if cron tasks fail due to blocked HTTP
requests
--------------------------------------+------------------------------
 Reporter:  prb22public@…             |       Owner:
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Cron                      |     Version:  3.5
 Severity:  major                     |  Resolution:
 Keywords:  dev-feedback needs-patch  |
--------------------------------------+------------------------------

Old description:

> I recently upgraded my very simple WP site to 3.5 where the following was
> in use:
>
> Theme: Twenty Eleven
> Plugins: None Activated
>
> I have been completely unable to submit a post for publishing in a future
> date, when the time occurs, I get a "missed schedule" message.
>
> The schedule entry in cron is as follows:
>
> Next due (GMT/UTC): Jan 4, 2013 @ 11:28 (1357298880)
>           Schedule: One-off event
>               Hook: publish_future_post
>          Arguments: [0]: 358
>
> Increasing the timeout value in cron.php has made no difference.
>
> I will need to remain on a lower release until this is fixed or a
> diagnosis "kit" is made available.
>
> I am not using any software other that WP produced at this point and feel
> that the lack of wp-cron documentation and support in the public domain
> leaves alot of people clocking many hours googling in desperation...
>
> Make a difference in 2013 and get 3.5 development priorities to de-
> mystify the methods of fixing wp-cron please :o)

New description:

 I recently upgraded my very simple WP site to 3.5 where the following was
 in use:

 Theme: Twenty Eleven
 Plugins: None Activated

 I have been completely unable to submit a post for publishing in a future
 date, when the time occurs, I get a "missed schedule" message.

 The schedule entry in cron is as follows:
 {{{
 Next due (GMT/UTC): Jan 4, 2013 @ 11:28 (1357298880)
           Schedule: One-off event
               Hook: publish_future_post
          Arguments: [0]: 358
 }}}
 Increasing the timeout value in cron.php has made no difference.

 I will need to remain on a lower release until this is fixed or a
 diagnosis "kit" is made available.

 I am not using any software other that WP produced at this point and feel
 that the lack of wp-cron documentation and support in the public domain
 leaves alot of people clocking many hours googling in desperation...

 Make a difference in 2013 and get 3.5 development priorities to de-mystify
 the methods of fixing wp-cron please :o)

--

Comment (by SergeyBiryukov):

 Related: #11831

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