I recently updated the webform module to 3.19. Now, none of my forms are allowing submissions. Users may see and fill out the form, but when they hit the submit button they get the note "You may not submit another entry at this time".

While poking around the webform trying to discover the problem I noticed the 'total submission limit' (under 'form settings') was checked to 'limit to'. I checked 'unlimited' and saved the form, but the change didn't take. The 'limit to' box was still checked after the save. I then tried giving it a limit (using a number much larger than the number of expected responses). Again, the change didn't take when I hit 'save configuration'. I then tried changing another part of the form and hit save. It did take, but going back and trying to modify the 'total submission limit' again wouldn't take. I don't know if this glitch is causing the other problem, but I suspect it is.

Anyone know what is going on? An quick response would be appreciated. The forms are heavily used, and we have already received multiple calls about them being down.

Comments

spitcher’s picture

I solved the issue by downgrading to the the version I had before 3.19. Anyone know why 3.19 didn't work for me?

quicksketch’s picture

I noticed the 'total submission limit' (under 'form settings') was checked to 'limit to'. I checked 'unlimited' and saved the form, but the change didn't take.

Did you run update.php after upgrading? Webform added a new database column to add support for a total submission limit. Previously we only had a per-user submission limit. If you didn't run update.php, Webform wouldn't have anywhere to save the value, which would explain why it wasn't taking.

spitcher’s picture

I did not. I assume that was is in the ReadMe file that I didn't read? Will it run when I click the file (which I assume is in the module folder), or do I have to do more to get it to update? (if the instructions are in the ReadMe file, just tell me and I will find it there).

Thank you!!!!
Sara

quicksketch’s picture

You'll need to run update.php after updating any module in Drupal (or Drupal core itself). The same process applies every time you update any module. The documentation on this isn't great, but there's a page at https://drupal.org/node/250790 detailing the process. You can usually skip the part about putting the site into maintenance mode, but I would definitely recommend you make a database backup before running any updates.

spitcher’s picture

Thank you! I will have to look into that and try updating everything again.

quicksketch’s picture

Issue summary: View changes
Status: Active » Closed (fixed)

Closing after lack of activity.