Posts: 15
Threads: 6
Joined: Sep 2010
Reputation:
0
Hi all,
I can't generate an Excel spreadsheet. When I attempt it, I get a blank page after the page initially hangs. What I get is a server connection error similar to when you try to access a site that isn't there. My client is freaking out. A real hothead. Need a fix fast.
Please, if there is anyone that can help it would be much appreciated. Can't seem to find the issue in the forum.
Thanks in advance.
Posts: 15
Threads: 6
Joined: Sep 2010
Reputation:
0
Sorry, the export script didn't receive all the required fields and cannot proceed.
Anybody ever get the above error?
Thanks.
Posts: 143
Threads: 19
Joined: Dec 2010
Reputation:
5
Aug 5th, 2011, 11:13 AM
(This post was last modified: Aug 5th, 2011, 11:14 AM by michatmaster7.)
I just realized that with the Export Manager I can show the option to use a CSV file instead of XLS (I'm a little slow). So I used the CSV option to export all 2500 or so records and I get the following error message:
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 1550172 bytes) in /home/{domain}/public_html/formtools/global/code/general.php on line 198
Is this a limit that cannot be lifted? Do I need to export records in smaller batches, no matter what?
Not a FT employee, just a FT user lending a hand. If I've been helpful, please rate.
Posts: 2,456
Threads: 39
Joined: Dec 2008
Reputation:
6
Hi michatmaster,
You *can* lift the limit, yes. The Export Manager is very CPU intensive - it does a great deal of work to generate the entire contents of a View / form, so memory can become an issue.
If you have access to the server's php.ini file, try updating the memory_limit directive to something higher than it is now. If you don't have access, perhaps ask your hosting provider on how you can do a customization for your site / folder. Some hosts have the server configured to let you define your own php.ini file in a folder that overrides specific settings like that one. Other hosts let you do that, but only by including the php.ini file in a cgi-bin folder. Other (for security reasons) don't let you do that at all.
If all else fails, you may have to resort to exporting the entire content in pieces (e.g. creating Views that show date ranges, or by specific content).
Good luck!
- Ben