After upgrading from v2.0 to 2.1.1 I have problems with modifying or submitting new fields to my existing form. I have a field type "email" (name: email) in the form and if I try to submit any other field, I receive this warning from Drupal:

user warning: Unknown column 'email' in 'field list' query: UPDATE webform_component SET pid = 27, form_key = 'FieldKey', name = 'FieldName', type = 'markup', value = 'FieldValue', extra = 'a:1:{s:6:\"format\";s:1:\"3\";}', mandatory = 0, weight = 10, email = 0 WHERE nid = 5 AND cid = 37 in /home/public_html/includes/database.mysql.inc on line 172.

Comments

quicksketch’s picture

You need to run update.php to bring the webform schema up-to-date. The e-mail column should be added to the database for you.

jazzitup’s picture

Even if I've run update.php two times, this time I did it by manually selecting Webform module upgrade "1" from the select box. And this time it worked. Thanks for the clue!

quicksketch’s picture

Status: Active » Closed (fixed)

If that worked for you, that's great. For anyone running across this thread, I'd discourage taking this same approach. It's very likely to break a bunch of things, running all the updates from 1. Generally, you should *never* change the the update function number, Drupal will select the number starting at the updates that have not yet been run. Update functions are not run-twice safe, as they'll try to run all the SQL queries again, even if it's not necessary.

Yasl’s picture

Version: 5.x-2.1.1 » 6.x-2.7
Status: Closed (fixed) » Active

Same error as above. What is the fix if you've run update.php several times and it still gives you the error? When upgrading to the latest it also lost data, it shows 29 submissions but I can only see the submission since the upgrade...

:(

Yasl’s picture

Since I could never get rid of this error I ended up completely uninstalling the 2.7 module and reinstalling the 2.6 which sends emails correctly. The 3.0 version gave me the same error btw.

quicksketch’s picture

Status: Active » Closed (fixed)

Note if you updated to 3.0 at any time, you permanently modified your database by doing so. You cannot downgrade to a previous version after upgrading the 3.0, which may have been where your problem arose.