I recently updated to webform 3.2 and started having issues when submitting the form. I have a webform with a single field "test" which is mandatory. In the webform configurations, when I have the webform set up to unlimited submissions, everything works smoothly and I am forwarded to the page I specified in the webform settings. However, when I set the webform to limit the submissions to 1, no matter whether I have usage of cookies enabled or not in the webform general settings, when I submit the form it simply loads the page again, keeping the values I entered in the fields. There are no error messages displayed or anything. I'd appreciate if you could let me know whether I'm the only one having this issue.
Comments
Comment #1
quicksketchI don't experience this issue when installing Webform from a fresh copy or on any of my current sites. Do you have any other webform-related modules installed (such as Webform Block)? Some Webform-related modules are not yet compatible with Webform 3.
Comment #2
aidinnz commentedThanks for the reply. I figured out that the anonymous user did not have permission to see his/her own submissions/results. This was causing the "you have already submitted this form" error to not show, hence the page would return an error, but it was not being displayed. I'm not sure what the functionality of Webform 2 was, but I think it's a good idea to show an error message to the user in this case (even if they don't have permission to see their own submissions/results). Otherwise it simply looks like the form is broken. Thanks again for looking into this.
Comment #3
aidinnz commentedComment #4
aidinnz commentedChanging the title to reflect the updated issue.
Comment #5
quicksketchUnfortunately the "you have already submitted this form" message cannot be shown if page caching has been enabled. If you turn off page caching it will show up as you expect. This is intentional behavior for performance reasons. If you allow anonymous users to edit their own submissions, then Webform actually disables page caching for that page, but it's not really recommended to enable editing of submissions for anonymous users anyway.
Comment #6
aidinnz commentedThanks Nathan. Is it perhaps possible to add another (separate) error message in the case when an anonymous user has already submitted their maximum allowed submissions without turning caching off? You can understand the usability issue when NO error messages are displayed to the user at all.
Comment #7
quicksketchThe error message is still displayed upon submitting the form (since submissions are never cached in Drupal). The only way to add a message to a cached page would be to insert it through JavaScript based on the user's cookies, which you can do through some custom coding since it's unlikely something like that will be included in Webform.
Comment #8
quicksketch