Closed (won't fix)
Project:
Import / Export API
Version:
4.7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
22 Jun 2007 at 11:04 UTC
Updated:
7 Dec 2007 at 18:11 UTC
Jump to comment: Most recent file
Comments
Comment #1
summit commentedHi,
The error I am getting is:
60M is a lot allready!
Can somebody help with this?
Greetings,
Martijn
Comment #2
Sunil Mohan commentedI've tried to make a small improvement in the way data is stored internally. I am hoping this will lead to big improvement in memory usage (although all data is still loaded into the memory before exporting).
I am attaching a patch made against importexportapi 5.x-1.x-dev (should also work for 4.7-1.x-dev). Can someone try this and let me know if there is any improvement?
This patch only works for export to xml from database (only db_get and xml_put are touched for now). If this works, I will finish this.
Comment #3
summit commentedHi,
I followed the patch, but I get a blank screen...
Tomorrow I will know why, because my ISP only sends me the errorlog tomorrow.
May be it's an easy mistake, I keep you posted.
Thanks for trying allready!
greetings,
Martijn
Comment #4
summit commentedI made a mistake. I missed a "$" I am not getting a blank screen anymore.
Greetings,
Martijn
Comment #5
summit commentedHi,
With executing I got a blank screen.
The error I get is:
I tried setting the executing time above 30 seconds with:
ini_set('max_execution_time', 120) in settings.php
or
max_execution_time = 1800 ; Maximum execution time of each script, in seconds
max_input_time = 600 ; Maximum amount of time each script may spend parsing request data
memory_limit = 100M ; Maximum amount of memory a script may consume (8MB)
in php.ini
without success.
Greetings,
Martijn
Comment #6
summit commentedHi,
To export Weblinks worked with the following settings in settings.php
Of course 200MB is a lot, but it worked!!
Thanks allready for your help!
greetings,
Martijn
Comment #7
summit commentedHi Sunil,
As expected I still get an error with importing in a drupal 5.1 site.
It didn't help to enhance the memory to 200MB.
The error I get is:
Please help to solve this!
Thanks in advance,
greetings,
Martijn
Comment #8
summit commentedNew error:
I get an http error 500 :(
Greetings,
Martijn
Comment #9
summit commentedHi,
I think the module overloads the CPU of the hosting server and the process is then killed?
I will wait for the import patch please.
Thanks in advance allready.
Greetings,
Martijn
Comment #10
summit commentedHi,
How is the import-side going.
I am very enxious to try it!
greetings,
Martijn
Comment #11
summit commentedHi Sunil, or any other who knows what to do,
It's a month later now, please also get the import from xml running please without out of memory error.
I am waiting for this for a website upgrade, which is to complex to do without this great module.
greetings and again thanks in advance!
Martijn
Comment #12
sunTo quote Jaza, the original author of this API:
4.7.x, I guess, won't fix anymore.