If I enable "Show complete form in teaser" for my MULTIPAGE webform (a webform with pagebreaks), and then promote it to the frontpage, strange issue appears after submitting the first page of a multipage webform from the frontpage:

Warning: MySQL server has gone away query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', '<em>MySQL server has gone away\nquery: UPDATE web_sessions SET uid = 1, cache = 0, hostname = &amp;#039;77.0.212.32&amp;#039;, session = &amp;#039;form|a:17:{s:32:\\&amp;quot;7860ed8b7bbd98db5e6994bce452a784\\&amp;quot;;a:2:{s:9:\\&amp;quot;timestamp\\&amp;quot;;i:1212862757;s:4:\\&amp;quot;args\\&amp;quot;;a:5:{i:0;s:21:\\&amp;quot;webform_client_form_5\\&amp;quot;;i:1;O:8:\\&amp;quot;stdClass\\&amp;quot;:30:{s:3:\\&amp;quot;nid\\&amp;quot;;s:1:\\&amp;quot;5\\&amp;quot;;s:3:\\&amp;quot;vid\\&amp;quot;;s:1:\\&amp;quot;5\\&amp;quot;;s:4:\\&amp;quot;type\\&amp;quot;;s:7:\\&amp;quot;webform\\&amp;quot;;s:6:\\&amp;quot;status\\&amp;quot;;s:1:\\&amp;quot;1\\&amp;quot;;s:7:\\&amp;quot;created\\&amp;quot;;s:10:\\&amp; in /home/milenium/public_html/includes/database.mysql.inc on line 172

Warning: MySQL server has gone away query: INSERT INTO web_watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', '<em>MySQL server has gone away\nquery: UPDATE web_users SET access = 1212863992 WHERE uid = 1</em> in <em>/home/public_html/includes/database.mysql.inc</em> on line <em>172</em>.', 2, '', 'http://localhost/reservation', 'http://localhost/', '77.0.212.32', 1212863992) in /home/public_html/includes/database.mysql.inc on line 172

I guess it's a session issue?! After I truncate a sessions table, I don't see those warnings after a page refresh, but I'm still uncapable to continue with filling my webform from the frontpage.

Questions:
Am I suppose to be able to continue with filling my webform with a several pages from a frontpage that way?
Is there a workaround if that's a wrong way to go?

Comments

quicksketch’s picture

I don't believe there's anything that Webform can do to actually disconnect your MySQL connection, as that's what looks like is happening. For reference, do you have the database prefix set to "web_"? Or is there a module using the tables "web_sessions" and "web_users"?

jazzitup’s picture

Yes, that's true - all of my Drupal tables do have a prefix "web_".

jazzitup’s picture

*** I still can't make this webform teaser work on a frontpage! ***

The only differences in an HTML I could notice between a form on the frontpage (a teaser) and the form displayed as a node are in these lines:

1. NODE (when a teaser doesn't exist):

<form action="/path_to_the_webform" ...
<input type="hidden" name="form_build_id" ...
<input type="hidden" name="form_token" id="edit-webform-client-form-5-form-token" ...

2. TEASER:

<form action="https://www.domain.com/path_to_the_webform" ...
<input type="hidden" name="form_build_id" ...

a) I'm using SSL for this webform, but the page is not encrypted (SSL) on a frontpage!
b) form_build_id have different id's and different values in both cases, which is normal
c) form_token only exists when a teaser is NOT set

jazzitup’s picture

It seems that this method solves an issue mentioned from above (more testing required):
http://drupal.org/node/259580

quicksketch’s picture

Does this really seem like it's a problem with Webform? If it's been caused by something else, please update the issue.

jazzitup’s picture

I assume that it was a session oriented issue. Now I'm testing a new release of a webform with this bug-fix:
http://drupal.org/node/275389

jazzitup’s picture

Title: Issue with promoting a multipage form to the frontpage » Issue with a multipage webform

This issue is still bugging me... I've removed the "promote to frontpage" option, so this issue is not related to it anymore and I believe it's not related to a webform module as well. After exactly 8 page reloads of the page that contains my webform (while testing) the warning from above suddenly appears below the content. Maybe I'll find my answer here: http://drupal.org/node/259580

jazzitup’s picture

Title: Issue with a multipage webform » Webform requires MySQL tuning

The link from the post from above was helpful... My ISP has solved the problem.

*** This issue was NOT related directly to a webform module itself. ***

quicksketch’s picture

Category: bug » support
Status: Active » Closed (fixed)

Thanks madjoe for the final word! I'll mark this as closed.