WordPress.org

Make WordPress Core

Opened 7 years ago

Closed 4 years ago

#8326 closed defect (bug) (fixed)

WordPress Importer Fails with timeout after 120 seconds

Reported by: JackWolfgang Owned by: duck_
Milestone: WordPress.org Priority: normal
Severity: normal Version: 2.7
Component: Import Keywords:
Focuses: Cc:

Description

PHP 5.2.6 on Apache 2.2.9 running on *nix with MySQL version 5.0.67-community

Running an import from WP 2.6 into 2.7 Beta 3 using the WRX file causes the following error:

Fatal error: Maximum execution time of 120 seconds exceeded in <snip of file path>/wp-includes/plugin.php on line 302

I tried this multiple times with two different WRX files, and it fails the same way each time. The file sizes are 600 kilobytes and 1,140 kilobytes.

Change History (15)

comment:1 @JackWolfgang7 years ago

  • Milestone changed from 2.8 to 2.7
  • Summary changed from WRX Import Fails in 2.7 Beta 3 to Updated Milestone

I'm not sure why that was set to 2.8 for a milestone. It would seem this should be fixed for 2.7's release

comment:2 @JackWolfgang7 years ago

  • Summary changed from Updated Milestone to WRX Import Fails in 2.7 Beta 3

Forgive my ignorance....posting my first bug here, and I didn't mean to change the summary.

comment:3 @ninjaWR7 years ago

  • Keywords 2nd-opinion reporter-feedback added

ENV 1: FreeBSD 7.0-RELEASE-p2 Apache/2.2.8 (FreeBSD) PHP/5.2.5 with Suhosin-Patch
ENV 2: Windows Vista SP1 Apache/2.2.8 (Win32) PHP/5.2.5

WXR: from 2.6.3, 1413.12 KB

WXR imports fine on both environments, although on ENV 1 it took a few seconds for it to get to the author selection page.

Tested on r9857

comment:4 @jacobsantos7 years ago

This has a known fix.

comment:5 @jacobsantos7 years ago

  • Keywords changed from 2nd-opinion, reporter-feedback to 2nd-opinion reporter-feedback

comment:6 @jacobsantos7 years ago

  • Summary changed from WRX Import Fails in 2.7 Beta 3 to WordPress Importer Fails with timeout after 120 seconds

comment:7 @jacobsantos7 years ago

Just needs to increase the timeout, if possible for the importer.

comment:8 follow-up: @jacobsantos7 years ago

Or get a faster host.

comment:9 in reply to: ↑ 8 @vladimir_kolesnikov6 years ago

Replying to jacobsantos:

Or get a faster host.

What about set_time_limit(0)?

comment:10 @westi6 years ago

  • Keywords 2nd-opinion removed
  • Milestone changed from 2.7 to 2.8
  • Owner set to westi
  • Status changed from new to assigned

Those import files don't sound particularly large.
This sounds like a slow host issue.

Can you:

  • Try running the import on a local install of 2.7 RC1
  • Share the WXR file privately with us to test with - email me peter dot westwood at ftwr dot co dot uk
  • How many Posts/Comments/Pages does the file contain.

Moving to 2.8 for now as I don't think this is a issue for a large number of installs.

comment:11 @Denis-de-Bernardy6 years ago

  • Milestone changed from 2.8 to Future Release

Punting to future...

comment:12 @Denis-de-Bernardy6 years ago

  • Milestone changed from Future Release to 2.9

comment:13 @ryan6 years ago

  • Milestone changed from 2.9 to Future Release

comment:14 follow-up: @ocean904 years ago

  • Keywords reporter-feedback removed
  • Milestone changed from Future Release to WordPress.org
  • Owner changed from westi to duck_
  • Status changed from accepted to assigned

Should be fixed with http://plugins.trac.wordpress.org/changeset/322932.

duck_ will do some final testing.

Related: #11144, #8326

comment:15 in reply to: ↑ 14 @duck_4 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

Replying to ocean90:

Should be fixed with http://plugins.trac.wordpress.org/changeset/322932.

duck_ will do some final testing.

Related: #11144, #8326

No time outs now for me.

Note: See TracTickets for help on using tickets.