Make WordPress Core

Opened 5 years ago

Closed 5 years ago

#14885 closed defect (bug) (worksforme)

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

Reported by: tj2point0 Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.0
Component: Upgrade/Install Keywords: reporter-feedback
Focuses: Cc:


Wordpress 3.0 installed on XAMPP. When I try to install a theme via built in search theme feature, I get errors. I tried to update WordPress to 3.0.1 from Dashboard >> Updates... it still shows similar errors, hence cannot update Wordpress. Following is the error shown when I tried to upgrade to version 3.0.1

 Fatal error: Maximum execution time of 60 seconds exceeded in H:\xampp\htdocs\wordpress\wp-includes\class-http.php on line 1060
Call Stack
#	Time	Memory	Function	Location
1	0.0056	521552	{main}( )	..\update-core.php:0
2	4.3335	26448880	do_core_upgrade( )	..\update-core.php:414
3	4.3492	26649992	wp_update_core( )	..\update-core.php:336
4	4.3640	27264896	Core_Upgrader->upgrade( )	..\update.php:249
5	4.3754	27268024	WP_Upgrader->download_package( )	..\class-wp-upgrader.php:878
6	4.3762	27268024	download_url( )	..\class-wp-upgrader.php:121
7	4.3826	27268800	wp_remote_get( )	..\file.php:492
8	4.3827	27268800	WP_Http->get( )	..\http.php:76
9	4.3828	27269256	WP_Http->request( )	..\class-http.php:361
10	4.3853	27273592	WP_Http_Streams->request( )	..\class-http.php:317

Change History (4)

comment:1 @dd325 years ago

  • Keywords reporter-feedback added

it appears that your hosting environment's internet connection is rather slow, Based off that stacktrace, it seems that during the attempt to download the .zip file, 55seconds later the Streams transport had not returned any data.

You can install the Plugin Core Control (that's one of mine), activate the HTTP Access module, and attempt disabling the Streams transport, By doing this, you'll be able to test to see if the WP_HTTP_Streams class running into a problem, or if it's purely related to your internet connecton speed.

comment:2 @hakre5 years ago

I suggest to close as invalid. If the original reporter does provide feedback again, it could be re-opened.

comment:3 @dd325 years ago

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.

comment:4 @dd325 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to worksforme
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.