[wp-trac] [WordPress Trac] #14885: Fatal error: Maximum execution time of 60 seconds exceeded in H:\xampp\htdocs\wordpress\wp-includes\class-http.php on line 1060 Call Stack

[WordPress Trac]

#14885: Fatal error: Maximum execution time of 60 seconds exceeded in
H:\xampp\htdocs\wordpress\wp-includes\class-http.php on line 1060  Call
Stack
-----------------------------+----------------------------------------------
 Reporter:  tj2point0        |       Owner:                   
     Type:  defect (bug)     |      Status:  new              
 Priority:  normal           |   Milestone:  Awaiting Review  
Component:  Upgrade/Install  |     Version:  3.0              
 Severity:  normal           |    Keywords:  reporter-feedback
-----------------------------+----------------------------------------------

Comment(by dd32):

 In the event that the reporter doesnt report back, like in every other
 ticket, It'll be closed after reasonable time has been allowed for them to
 get back. There's no harm in leaving it for longer than 48hours.

 Whilst there's no harm in having someone re-open a ticket, I feel its
 kinder to people who don't understand the ins-and-outs of tickets to leave
 it open for as long as reasonably possible.

 One example of why I take this approach, is a Well known Australian ISP
 will leave a ticket open forever if you do not specifically close it,
 Another ISP closes the ticket as soon as they've replied to it, putting
 the onus back on the ticket opener to re-open the ticket if they still
 require help.  As you can probably guess, Many users of the latter ISP
 will complain their ticket was just closed without any thought or
 explanation, whilst users of the first will always mention their ISP is
 great, because they are willing to help them out as long as they're having
 the problem. It all comes down to perception & timing.

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