We use Webform (along with Webform Bonus Pack and Form builder Webform UI) to build forms that volunteers use to report findings from site visits. The problem we are having is that when a volunteer clicks on a link for a particular form (in order to fill it out anew), it is pre-populated with that user's most recent previous submission. I originally thought this was a browser caching issue, but now it appears that what is really happening is that clicking on the link for a particular node in fact brings up the most recent past submission in edit mode. The volunteer then fills it out, erasing the old data, and submits. This means the original submission is overwritten.
Is there anything I should look at, settings-wise, to take care of this issue? I don't think the behavior is 100% replicable, but it happens enough that it's a problem.
Apologies if this has already been asked and answered - I couldn't turn up anything in a search.
Comments
Comment #1
danchadwick commentedIt sounds like you have drafts enabled, and the user has not completed his draft.
If you want multiple drafts, you need to implement HOOK_webform_draft_alter().
Comment #2
tmccartney commentedTo make sure I understand: If there's an unsubmitted draft, the user's next attempt to start a fresh form will instead load up the last draft?
Also, not only do I have the "save draft" button enabled on each page, I have it saving drafts every time the user goes to the next page.
Comment #3
danchadwick commentedYes, unless you implement the hook I mentioned, which allows multiple simultaneous drafts. And in that case, you are responsible for somehow getting the user to complete the drafts.
Your simplest solution might be to disable drafts.
Comment #4
tmccartney commentedThanks, Dan. I will give that some thought.