Closed (won't fix)
Project:
Webform
Version:
6.x-2.10
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Aug 2008 at 21:54 UTC
Updated:
30 Jun 2015 at 09:03 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
errement commentedI am having the same problem, shouldn't WebForm module set this regards to IP of the anonymous user?
I did a questionnaire too and wanted to allow all users to do it just once (1 ever). It only works for registered users.
Comment #2
dan3h commentedI too had the exact same problem. Was set to allow only "1 ever" submission per person, and it ended up only allowing one anonymous person to submit the form. (I tried accessing it from different browsers, and also from completely different machines, with IP addresses that are for sure different.)
Had to change it to "unlimited" submissions to get it to work.
Comment #3
daniel korteI had this problem to and it seems to be fixed for me now.
The logic to check if the Unauthenticated user has already submitted a webform fails because it only checks that the uid = 0 and the ip address equals any one of those in the webform_submissions database table.
The scenario where a user logs in, submits a webform and then logs out would have no access to the webform as an unauthenticated user because their ip address matches that in the webform_submissions database table. My patch checks that the uid in the table (0 for Unauthenticated user) also matches the current user who is also unauthenticated (0).
Comment #4
quicksketchI think this is the intended behavior, would you really want a user to be able to submit as a registered user, logout, then submit the same form again?
Comment #5
daniel korteI think it makes the most sense to allow this.
Consider a shared computer such as at a library or university (such as where I am). If a user uses a computer at the local library to submit a webform then logs out anyone who trys to submit a webform from that computer from then on out cannot do so.
Also, I'm not exactly sure how wireless networks work but (now I may be wrong here) at my house it seems that we all have the same IP address which means two of my roommates who do not have an account but may likely use the webform cannot do so since I've already used it.
Comment #6
deemunk commentedI'm having similar problem. I need to allow users with same IP address to be able to fill the same form but need to limit submission based on the email address they input. However it seems like submit limit check only looks at the user's IP address. Does anyone know if there is a way to add a different criteria (for example email field from the form), without having to mess with the module code?
Comment #7
ebeyrent commentedI had the same problem - anonymous users could keep re-submitting the form. I applied the patch and that fixed it.
Comment #8
tech@rivernetwork.org commentedI am looking for the same functionality.
We need to be able to allow multiple anonymous submissions from the same IP address, but only allow 1 submission per email address. It seems like there would be an easy way for the form to compare the email address field with what has already been submitted, and deny the submission if that address is already in the database. Anyone?
Comment #9
mkalkbrennerWe ran into a related issue.
We have a form that's restricted to authenticated users and any user is allowed to fill out the form only once.
But as soon as one single authenticated user completed the form, anonymous users from the same IP get the message that they already completed the form instead "You need to login or register ...".
Same IPs occur very often. Most companies use firewalls or routers for their outgoinig traffic. In this case hundreds of employees are using the same IP!
The reason for our problem is the same as described at comment #3. _webform_submission_limit_check() simply returns a wrong value for both use cases.
But I adjusted a patch that's simpler than the one from #3.
What the function is doing now is limit anonymous submissions per IP regardless of non anonymous submissions from the same IP.
From my point of view the downside described in #4 is less important than fixing the current issues. The check for cookies which is also available addresses the issue described in #4 even better.
Comment #10
quicksketchConsidering we haven't heard anything in this issue for 9 months, I'm assuming it was corrected in later releases of the module. If this problem still exists in the 3.x versions, please reopen.
Comment #11
mkalkbrennerWe still use the latest 6.x-2.x version including the patch from #9.
Unfortunately I don't have time to evaluate 6.x-3.x the next days.
Comment #12
quicksketch2.x is no longer receiving updates.
Comment #13
jaskaran.nagra commentedFor Drupal 7, you can use the Webform per Email module to allow one time access to anonymous users via their emails.
Thanks,
Jask