https://legacy.forums.gravityhelp.com/topic/problems-exporting-entries Gravity Support Forums Topic: Problems Exporting Entries en-US Sat, 04 Apr 2026 19:17:23 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/problems-exporting-entries#post-42914 Fri, 02 Dec 2011 16:22:42 +0000 marvinforte 42914@https://legacy.forums.gravityhelp.com/ <p>Great. Thanks guys. Rackpace increased the memory to 128MB and they seemed to do the trick. I can export all entries for now. </p> https://legacy.forums.gravityhelp.com/topic/problems-exporting-entries#post-42317 Mon, 28 Nov 2011 16:43:20 +0000 Carl Hancock 42317@https://legacy.forums.gravityhelp.com/ <p>It's a memory issue. The error reported above is an out of memory error. This means you need to increase your available PHP memory further. 32 MB is a relatively small amount. Ideally you should have a minimum of 64 MB but i'd actually recommend 128 MB or more for most sites. The more data and the larger the form, the more processing required to parse and return that data. You'll need to increase the memory to more than 32 MB. I would suggest 64 MB or ideally 128 MB. </p> https://legacy.forums.gravityhelp.com/topic/problems-exporting-entries#post-42288 Mon, 28 Nov 2011 12:45:19 +0000 WESCONet 42288@https://legacy.forums.gravityhelp.com/ <p>I was experiencing the same issue trying to export my form with ~235 fields. The fields are all short text and numeric data. PHP was set to 64M of memory and no errors are being logged by apache in the error_log. Increasing the PHP memory limit to 96M fixes the problem.</p> <p>On another note, submitting the form is also taking quite a long time, users were double submitting before I added some jquery to disable the button after submit. </p> https://legacy.forums.gravityhelp.com/topic/problems-exporting-entries#post-41624 Fri, 18 Nov 2011 21:04:55 +0000 Chris Hajer 41624@https://legacy.forums.gravityhelp.com/ <p>305 fields per entry? Wow. Is it possible to increase the memory to 64MB or 128MB as a test, even though there are no memory errors being logged. All signs point to a PHP memory issue.</p> <p>The alternative is to export more frequently for shorter time spans. Smaller chunks will probably not run into the php memory issue. </p> https://legacy.forums.gravityhelp.com/topic/problems-exporting-entries#post-41620 Fri, 18 Nov 2011 20:51:27 +0000 marvinforte 41620@https://legacy.forums.gravityhelp.com/ <p>Yes, after they increased the RAM, we still have an error. Rackspace said "does not appear to be generating direct PHP errors" after the memory increase but I still can't export the entries.</p> <p>There are 280 entries, about 305 fields. No large quantities of text, no uploads. </p> https://legacy.forums.gravityhelp.com/topic/problems-exporting-entries#post-41611 Fri, 18 Nov 2011 20:25:59 +0000 Chris Hajer 41611@https://legacy.forums.gravityhelp.com/ <p>After they increased the RAM you still have an error? What errors are logged when it fails now?</p> <p>You are running out of memory when trying to export a large set of entries. Short of analyzing the plugin to find room for improvement, you need to get more RAM from your host. Unless you are getting a different error now, with 32MB of RAM. If so, please post that error.</p> <p>Can you describe the data you're trying to export? How many entries and how much data in each entry (number of fields, any large quantities of text or anything stored in the entry)? </p> https://legacy.forums.gravityhelp.com/topic/problems-exporting-entries#post-41609 Fri, 18 Nov 2011 20:15:42 +0000 marvinforte 41609@https://legacy.forums.gravityhelp.com/ <p>I am having problems exporting entries of this form:</p> <p><a href="https://loanapp.firstamerican.org/" rel="nofollow">https://loanapp.firstamerican.org/</a></p> <p>I can specify a small range of a few days and sometimes successfully export a CSV file.</p> <p>If I leave the date fields blank or specify a wider range, I get this error:</p> <p>Firefox can't find the file at <a href="https://loanapp.firstamerican.org/wp-admin/admin.php?page=gf_export" rel="nofollow">https://loanapp.firstamerican.org/wp-admin/admin.php?page=gf_export</a> OR I get a blank CSV file.</p> <p>I've had my webhost increase PHP memory to 32mb.</p> <p>Here's what they said:</p> <p>"I have checked your server PHP logs sent to /var/log/messages, and I do see some evidence that would point to a PHP memory limit issue, though it is not definitive. First, /var/log/messages will store logged information related to a PHP monitoring module - Suhosin. This module shows warnings that WordPress is attempting to allocate 32 MB of memory and is getting rejected as this is over the value defined in your /etc/php.ini:</p> <p>[root@firstamerican vhosts]# tail -1 /var/log/messages<br /> Nov 10 14:46:50 firstamerican suhosin[31791]: ALERT-SIMULATION - script tried to increase memory_limit to 33554432 bytes which is above<br /> the allowed value (attacker '127.0.0.1', file '/var/www/vhosts/loanapp.firstamerican.org/wordpress/wp-includes/default-constants.php',<br /> line 43)</p> <p>Additionally, I checked the Apache error log to see if this script was generating any out of memory errors related to this, but I could not find any. Finally, I have checked your Database size for the 'firstamerican' database, and it is not large enough to cause any MySQL related memory errors.</p> <p>To mitigate these issues with your form, I have increased the memory_limit in /etc/php.ini from 16M to 32M. This has halted the Suhosin alerts, I expect that this will resolve your issues; however, since this does not appear to be generating direct PHP errors I cannot be certain. If you continue to see any issues, please let me know exactly how I may replicate them. I would like to make sure that your Wordpress installation is operating to your satisfaction."</p> <p>After that, the problem was still happening, so they have also increased the following values in php.ini:</p> <p>upload_max_filesize<br /> post_max_size<br /> max_execution_time<br /> max_input_time<br /> memory_limit </p> <p>The issue is still happening and I'm not sure what to try next. </p>