Using latest CVS version of node_import. This seems like it would be a function of my local dev environment but I never got this problem before. Apologies if it is my fault.

When import lasts more than 60 seconds the import aborts and I get this error messgae:
Fatal error: Maximum execution time of 60 seconds exceeded in C:\workspace\mysite\includes\common.inc on line 422

Is there any chance that the latest changes to node_import would cause this error?

Comments

dado’s picture

dado commented

naturally i can make this go away by adding this to .htaccess file

php_value max_execution_time 1200

Robrecht Jacques’s picture

Robrecht Jacques commented

Like you said before: the geo-stuff takes a while, but that's the only thing I can think of. The other things are really straighforward copies of variables, so that should take too much time.

However, if one would import 1000 nodes in one CSV file, one is likely to get a timeout. I'll check how we could avoid that (which may be related in providing a "progress-bar" to the last page -- a bit similar to how update.php works, but I'll need to check this more closely).

budda’s picture

budda
Primary language English
Location Cheshire
commented

I get the same issue. Times out on line 416.

Can you not just add a set_time_limit(0); before the main loop to make this go away?

I've not looked at the module code, but this usually fixes intensive processing time outs. I'm parsing a 10.5MB CSV file so it keeps failing on me unless I stick the above time limit line in to the module.

Robrecht Jacques’s picture

Robrecht Jacques commented
Status: Active » Closed (duplicate)

See: http://drupal.org/node/64512