Closed (fixed)
Project:
Webform
Version:
6.x-3.0-beta4
Component:
Code
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
12 Apr 2010 at 14:53 UTC
Updated:
7 Jun 2010 at 22:24 UTC
Hello,
Its been 2 hours that I'm reading every issue posted here, I have done everything explained in these posts but still I cannot get anonymous users to submit webforms. I've upgraded to 3.0beta4 but nothing has changed. Can somebody help me to fix this please?
Comments
Comment #1
quicksketchAre you getting a message saying that the users are required to login? What do anonymous users experience when they visit the URL of the webform?
Comment #2
egunay commentedOk so,
Anonymous users can see the form without any problem. So they have the permission to access the form, form compenents etc. But when I try to submit the form after filling it in I get redirected to login page. As I said I've looked nearly every related issue and done everything written but nothing has changed. Do you have any idea about what can cause this error.
Thanks for your attention.
Comment #3
egunay commentedI don't remember exactly in which issue I've seen but I remember that someone was saying some module had a conflict etc. Is there any known conflicts, so that I can check my modules maybe?
Comment #4
quicksketchIt sounds like anonymous user sessions are not working. You'll probably find that anonymous users do not get confirmation messages (in the message area) when they use the contact module or any other form in Drupal. So check that the following things are happening: 1) anonymous users are assigned a cookie. This may not happen if you have some performance optimizations on your server, like if you're using Varnish or Pressflow. 2) Make sure that anonymous users are getting assigned a session in the session database table. 3) Make sure that the uid 0 is in the users table.
Comment #5
egunay commentedThanks for your answer but still nothing?!
I'm going to get crazy here...
Do you have any other suggestions? :)
Comment #6
egunay commentedBy the way yes, anonymous users are not getting confirmation messages.. For example I tried to request a new password entering some mail, but it redirected me to login page again without any message or error...
I have the user 0 in my database, and as far as I understood my sessions are also working but I'm still having this problem.
Comment #7
egunay commentedHello,
I'm so sorry about everything but it was my mistake... Some error that I've made on my custom template was causing this.
Sorry again for taking your time. It works perfectly.
Comment #8
quicksketchComment #9
arcaneadam commentedquicksketch I've got a similar issue and after reading #4 I realized that the site is using both Pressflow and Varnish. I'm just wondering if you have any fixes or ideas on how to make webforms work in that setup.
Comment #10
quicksketcharcaneadam: Webform *should* work just fine with Pressflow/Varnish. I was just suggesting it as a potential caveat if you're having Varnish eat all your anonymous cookies (which is not common). Webform starts a session as soon as you fill out a form, which will give anonymous users normal behavior as if you were using normal Drupal, and they should pass through Varnish once they have this session cookie. By default Varnish doesn't cache any page that has a cookie at all.
Anyway, I don't think this is the appropriate place to discuss Varnish. If you're using it, you should be able to configure it to work just fine with Webform. Otherwise, Lullabot is available for consulting work ;-)
Comment #12
sethviebrock commentedSame issue: Pressflow/No Varnish (dev) -> Pressflow/Varnish (live) -> inconsistent behavior for anon users (works on dev, not live).
Resolution: Set submission limit to unlimited. Was set to 5 submissions ever, setting to 5 submissions per hour seemed to work but didn't want to spend time / risk debugging, so just opened it up completely.
Comment #13
sethviebrock commentedI also should mention that we added a Varnish rule to ignore the form's URL and not cache the form...but that didn't resolve the issue initially.