Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Updating from 1.14 to 1.15 broke all my webforms.
Trying to fill out the forms returns HTTP 500 errors.
Using PHP 5.6
Is anyone else getting this problem?
Downgrading to 1.14 solved the problem.
Comments
Comment #2
Liam MorlandI haven't seen or hear of this problem. We're using PHP 5.6. You could use
git bisect
to figure out which commit it causing the problem.Comment #3
lustratus CreditAttribution: lustratus commentedI was having this problem as well; I don't recall if I had just updated webmin or not, although I did run several updates that day. I tracked it down to a few lines in webform_rules.rules.inc.
I'm using PHP 5.6 as well.
I had to make these changes:
if (empty($submission) || !$submission[$first_key]->nid ) {
changed to:
if (empty($submission) || empty(array_values($submission)[0]->nid)) {
I also made a similar change a few lines down:
if(!empty($selection['webform-client-form-' . $submission[$first_key]->nid )){
changed to:
if(!empty($selection['webform-client-form-' . array_values($submission)[0]->nid])){
Comment #4
lias CreditAttribution: lias commentedI'm experiencing the same issue with 7x4-15 and getting intermittent user feedback that they submit the form and get the 500 error. Using PHP 5.6 as well.
I have forms set to email the submissions and do receive the submitted form but the user ends up duplicating the submission because they think it failed.
@vchen - how did you downgrade to 4.14? I wasn't sure if the 4.15 updated the database and would break my forms.
@jeeberpow - I'm not seeing that webform_rules.rules.inc in the webform 4.15 module directory. Where exactly is this file?
Comment #5
vchen CreditAttribution: vchen commented@Isabug - I probably deleted 4.15 and redownloaded 4.14 and run drush updatedb.
I forgot about this issue actually and had updated back to 4.15 a while ago and somehow the problem isn't being reported anymore.
Comment #6
lias CreditAttribution: lias commentedThanks for the update @vchen.
Unfortunately I'm still experiencing it but it's not consistent with the error at all, - I'll try deleting 4.15 on my dev site and replacing with 4.14 and see what happens.
Comment #7
lias CreditAttribution: lias commentedTo follow up, I downgraded to version 4.14 and the error disappeared.
Comment #8
Liam MorlandIt would be great if you could use
git bisect
to identify the problem commit.