| Post |
|
Guest
| Dalton 3:51 pm December 18, 2008
| |
|
|
Please replace the ??? with your data!
- URL to the FORM: http://???
- The browser used: Firefox
- cforms version: 9.3
- Your Wordpress version: 2.65
Hi Oliver,
I have been using cForms for quite a while, and now am having a little bit of trouble. We recently moved to a new server, upgraded WordPress to 2.65 (from 2.6.3) and upgraded cForms (from 8 to 9.3) all at the same time. Therefore it's a bit tricky to troubleshoot exactly what caused the problem.
When we try to do a CSV export (or any kind of export),the resulting page is blank and there is no download. We are not using any filters of any kind. Can you think of any reason this might happen or let me know what kind of things I can do to troubleshoot?
Thanks,
Dalton
_
|
|
|
Admin
| Oliver Munich, Germany posts 6237 8:26 pm December 18, 2008
| |
|
|
Reading between te lines, I understand that
- the tracking page displays the data well
- you can use the filters on the existing data
can you confirm?
|
|
|
|
|
Guest
| Dalton 5:33 pm December 19, 2008
| |
|
|
Hi Oliver,
That is correct, the tracking page is working just fine and I am able to use filters on the tracking page. In fact, I just tried filtering the results and generating an export, which ran successfully (about 200 records).
On an unfiltered query, when I click the export button, the popup window to select my format works, but no matter what format I choose it just goes to a blank page (lib_database_dlentries.php) and does not generate the file.
I have tested this on multiple computers with the same result.
The SQL query performed in lib_database_dlentries.php seems to be fine. When I run:
SELECT *, form_id FROM cms_cformsdata,cms_cformssubmissions WHERE sub_id=id ORDER BY id desc, f_id ASC
directly against the database, I get about 900 records (15000 rows) returned.
Do you think this is a timeout issue? It worked fine on our shared hosting account, it seems strange that we just upgraded to a new server with more resources and all of the sudden the query is failing.
Thanks,
Dalton
|
|
|
Admin
| Oliver Munich, Germany posts 6237 6:57 pm December 19, 2008
| |
|
|
I can't replicate the error here, but even a timeout should not result in a white screen, since the download is triggered in parallel so to speak.
So the download popup window (from your browser) does appear for smaller files? Have you tried to gradually increase the return results to see if it indeed is connected with the volume of returned results?
Also, you could try to set a fake filter. Just search for something that all sets have and try that – could be an issue with not having a filter set at all.
|
|
|
|
|
Guest
| Dalton 7:31 pm December 19, 2008
| |
|
|
Aha! I finally got an error message. It seems that the limit is somewhere between 300 and 400 returned records in a query… any more than that and I get the blank page.But, I ran a query that resulted in 417 records, and got this error:
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 71 bytes) in /home/storyc/public_html/wordpress/wp-content/plugins/cforms/js/include/lib_database_dlentries.php on line 121
My memory limit was 32MB, I upped it to 64MB and that did the trick.
I will make sure that the database is emptied from time to time so that we can do the export when we need to. Thanks for the advice.
|
|
|
Admin
| Oliver Munich, Germany posts 6237 7:45 pm December 19, 2008
| |
|
|
glad we found the culprit. it must be also a matter of the number of fields per form, because way back I remember doing tests with smaller forms (4-5 fields) and downloaded more than 20,000 records.
the mentioned line is:
$entries = $wpdb->get_results($sql);
which indeed shows that the memory allocation by $entries caused the error, due to too much data being returned by the SQL call.
I'll see if I can find ways to do this differently, but suspect it would be on the expense of the SQL server (e.g. requesting data sets individually in a loop).
|
|
|
|
|
Guest
| Craig 8:23 pm January 22, 2009
| |
|
|
Can you tell me where you up'd your memory limit? I may be having the same problem. Is that in code somewhere? Or server cPanel? Or in WordPress?
Thanks,
Craig
|
|
|
Admin
| Oliver Munich, Germany posts 6237 7:37 am January 22, 2009
| |
|
|
Usually you can put the new config statement into a php.ini file in the respective folder, or add a statement to the code set_ini();. Try Google or ask your provider which is the best/correct (for them) route…
|
|
|
|
|
Guest
| gulflee 8:49 am February 14, 2009
| |
|
|
I had found a way, just increase the wp-setting.php
define('WP_MEMORY_LIMIT', '64M');
that will fix the blank screen
|
|
FAQs
Reply to Post
Add a New Topic
Search 
cforms II User Forum
Quote and Reply 
Topic RSS 
