Closed (fixed)
Project:
Webform
Version:
5.x-1.8
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Jan 2008 at 19:45 UTC
Updated:
13 Apr 2008 at 01:54 UTC
After upgrading to fix the issue I brought up here: http://drupal.org/node/211293 I'm now seeing a blank white screen when i try to edit the form. I can view the results without issue, but I'm unable to edit the form. I tried to edit another webform on the same site and it worked just fine. I did notice that the webform did not have any date components.
I cloned the webform that didn't have dates, added a date, and saved it. I was able to edit this one just fine. Is it possible that there was a problem with the upgrade for the form that had date components before the upgrade?
Comments
Comment #1
quicksketchAh, the old blank white screen... turning on php errors will give you (and me) a better idea of what went wrong. In your php.ini file could you set these two flags?
display_errors = On
error_reporting = E_ALL & ~E_NOTICE
Comment #2
GoofyX commentedThis node is also helpful for debugging such errors.
Comment #3
safetypinWell, downgrading fixed the error. We were also getting errors submitting the web form. Apparently the dates were all being interpreted as invalid dates. We're going through the testing phase right now, so I'll find time to upgrade the script and do proper debugging as suggested and post the results here as soon as possible.
Comment #4
safetypinOk, turned out I had time now. As a control, I attempted to recreate the situation in a new form, by creating a form with a date component while webform 1.7 was installed. Unfortunately there must be specifically something wrong with the form as I created it, because I do not get the WSoD on the new form. The error (I'm guessing it won't be too helpful) follows:
---
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 2638991 bytes) in /var/www/vhosts/mysite.com/httpdocs/includes/common.inc on line 2188
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 130 bytes) in /var/www/vhosts/mysite.com/httpdocs/includes/database.inc on line 79
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 130 bytes) in /var/www/vhosts/mysite.com/httpdocs/includes/database.inc on line 79
---
Unfortunately, we're working on a client's host, not our own. It's a shared hosting solution, so we probably won't have much control over the server. Perhaps not even SSH access. Since it *works* at version 1.7, I'm gonna go ahead and leave it downgraded for now. The form I'm working with is ridiculously long, and I don't want to recreate it. I may try removing the date fields from the form and then upgrading, maybe that will help debug.
Comment #5
quicksketchOh dear. I can see why 1.8 would cause such a message, that's very unfortunate :(
1.8 takes into account better sorting of elements and returns emails, csv files, and results in the proper order according to fieldsets. 1.7 sort of just jumbles them all together. To do this, there's a lot of recursive logic that could potentially take a lot of memory. Apparently in your case you used up all the memory available. Exactly how big is your form?
You can usually solve this problem by setting a new memory limit in your Drupal settings.php file.
Find all the ini_set() calls towards the bottom of settings.php and add this line beneath the existing ones:
Your memory limit is currently 32M. I'll see if there are ways I can reduce the number of recursive function calls. To prevent this error from becoming wide-spread.
Comment #6
safetypinWhen I say "ridiculous" I mean it. I just counted, and by my count, the form has over 190 components. Part of the problem is, we've got probably 10+ different addresses that need to be captured, so with Street/City/State/Zip that's forty textfield components right there. This form is almost certainly an exception to the rule. I did remove the ten date components from the form (while in v1.7) and after upgrading to 1.8, it worked properly. So, I guess this means the form is just barely reaching the memory limit.
What we're dealing with here is a credit application. So, we're collecting current/previous addresses, contact information for current employers, employment history, references, co-applicant information, etcetera.
Comment #7
quicksketchComment #8
quicksketchThe 1.9 and 2.x versions are more efficient and require less recursion than 1.7, hopefully this should prevent the problem you're reporting with running out of memory.
Comment #9
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.