Component not saved/created

I'm not getting this problem on my own installations of Webform. Do you have any other Webform-related modules installed?

Same here. On my site it happens to nodes that are not of the type 'webform' but have been selected as allowed node types to contain a webform. When adding components I also receive the message 'New component [NAME] added' but that is simply not the case. On 'webform' nodes everything works great.
Thanks in advance.
Best regards,
Björn

This happens to me on the webform 7.x-3.4 beta1 too. This happens on the webform content node created by webform install. Actually I was able to successfully create a form and test its submissions. However I needed to add, edit and reposition few components/fields but it just does not happens. When I add a component field I get a success message that it has been successfully added but it does not show on the actual form page. The component actually gets added to the component list. I even tried to convert the text format settings to Full HTML but it was of no use.

The Drupal 7 version is (again) broken due to new API changes in Drupal 7 beta2. Please keep Drupal 7 issues separate.

Mine is exactly the same case as with #3 ie. works as webform node itself but not on the "Story" node.

I am getting the same problem, except that I am even getting it on my nodes of type webform. I've attached a screenshot.

I have these modules:
Calendar
Date
CCK
Filefield
ImageAPI
ImageCache
ImageField
Lightbox2
LoginToboggan
MailChimp
PathAuto
RememberMe
Rules
ThemeSettingsAPI
Token
Ubercart
Views
WebForm

@hypatia7777: You're clicking "Submit" instead of "Add".

Also seeing this issue. Trying to add a textfield to a new webform in Drupal 6.19. I see the field in the database but it doesn't show up on the form. This happens when creating a Webform node.

When viewing a newly created webform I get the following message:

user warning: Unknown column 'block' in 'field list' query: INSERT INTO webform (nid, confirmation, confirmation_format, redirect_url, block, teaser, allow_draft, submit_notice, submit_text, submit_limit, submit_interval) VALUES (426, '', 0, '', 0, 0, 0, 1, '', -1, -1) in /www/includes/common.inc on line 3528.

If the "block" column is missing, you probably need to run update.php. This column was added in the 3.3 version of Webform.

I ran it but the problem still exists.

ornj: The "block" column is added in Webform Update 6321. If this column doesn't exist, it sounds like your update didn't run properly and your installation is now incorrect. I'm not sure what to suggest here since once your database gets out of sync with where Webform/Drupal expects it to be, there's not much that can be done other than manually fixing the database. In your case, you may be able to fix things by manually running update 6321 from update.php, but it sounds like your database is beyond the help I can provide in the issue queue.

I'm not a db person but I know enough to poke around. There is a "block" column in the webform table. Is that the column you are referring to?. Could I just uninstall the Webform module and reinstall the latest version? I haven't created many forms yet so it wouldn't be a big deal if it would solve the issue.

* Uninstalling the module and reinstalling seemed to fix the issue.

There is a "block" column in the webform table.

I'm not sure how it'd be possible that there's a block column in the table but you'd be getting an error saying that it's not in the table:

user warning: Unknown column 'block' in 'field list' query: INSERT INTO webform (nid, confirmation, confirmation_format, redirect_url, block, teaser, allow_draft, submit_notice, submit_text, submit_limit, submit_interval) VALUES (426, '', 0, '', 0, 0, 0, 1, '', -1, -1) in /www/includes/common.inc on line 3528.

Those sound like they're at odds with each other.

But in any case, yes you could disable and then uninstall the module to start all over.

I'm having the same problem as #3 and #6. Webform content type works, Page content type which is webform enabled doesn't show the components even though they are in the database.

I've disabled and uninstalled webform then re-enabled it and the problem is still there.

Currently running through the module list for anything conflicting but nothing stands out.

More info: It looks like an entry isn't being created in the "webform" table for content types which aren't webform.

I manually added the corresponding nid into the webform table, using table defaults for the other fields, and the components are now showing in both the component list and the form view itself.

The problem only occurs when adding a form to content which was created before the content type was webform enabled.

For e.g. now that Page is webform enabled, when I create a new node of type Page, the webform works.

More info provided - updated status.

Confirmed.
And here is why.

If you webform-enable a content type that already has existing nodes, that node does not have an entry in the {webform} table yet.
Webform is programmed to add an entry to that table on the node update.

Here is the problem.
If the first thing you do is try to add form components to any of those existing nodes BEFORE YOU UPDATE (re-save) that node...
The components are added, but because webform does not have an entry in the {webform} table yet, you will not see your components.

*Temp*
To fix this for now, just edit and save the node.
This causes Webform to run it's {webform} check and it will insert your node entry for you.

What we'll need to do is run the check code found in the webform_node_update function (webform.module line 904-911) when components are added / updated... or something to that extent.
We could add this when the Webform tab is loaded (webform_components_page) or when a component is inserted / updated.

Thanks for the sleuthing Dan. It probably only makes sense to make an entry into the webform table when a component is actually added, not when the page is simply viewed. I think there are two ways of handling this, we could probably set a flag in $node->webform for containing the defaults just by updating webform_node_defaults(). Then if a node was using the defaults we'd make sure to node_save() the whole node also to make the webform entry. The other option is just to use node_save() all the time when adding new components, which would have the end-result of creating the webform entry also. I'm leaning more towards the first option, since node_save() is generally an expensive operation, especially if you have a lot of other modules enabled for modifying nodes.

I have posted my issue at #6 and I'm please to report that the temp fix by @djalloway "works".

Many thanks indeed @djalloway.

Having the same problem as #7 (@quicksketch(#8):when clicking on "add") even for the content type webform. Partially solved following the temp fix by djalloway in #18: works if I use the English interface to make webform edits, but fails if I use the German interface for the edits.

Same problem here. Neither can I add Webform Components nor Email-adresses.

Tried to downgrate to Webform 6.x-2.10 but to no avail since Webform did not appear in the module list.

When I run update, I get the following message:
webform module can not be updated. Its schema version is 2. Updates up to and including 20 have been removed in this release. In order to update webform module, you will first need to upgrade to the last version in which these updates were available.

Don't know what to make of this message since I do have the latest version installed.

#22, you should read the module page in full: http://drupal.org/project/webform

Under the heading "Upgrading from Webform 2.x to 3.x":

You cannot downgrade to 2.x once you have updated to 3.x. Make a database backup before upgrading.

Hi guys, had much the same probs, upgraded, would not create.... It is a permissions issue, check them all. Works fine now and created a content type all it's own. Great module. Thx

A patch has been proposed in #1008514: Enabling webform for an existing content type, then trying to add webform components to an existing node, fails. , so I'm marking this duplicate. Please follow up in that issue.

This still happens on the last version. I cannot add any component to any webform node, either the default "webform" or other enabled content types. No error report, just a silent failure. The weborm_component table stays empty
Webform works well in other sites on the same code install, it fails on a rather simple site while working on a much more complex.
I tried to uninstall, reinstall with no success.
#25 is about another issue, and is for D7

@jvieille: I doubt this is the same issue since it's been 2.5 years since this was created. If this were still a problem with all installs, the 150,000 D6 users surely would have reported it. So I don't think this is an issue with a clean install. During your un-installation, did you actually use the UI option for uninstalling the module (which drops all the existing tables)? Just disabling/deleting/replacing the module doesn't fully uninstall it.

Thanks for taking care.
Yes, I uninstalled the module ad even removed the webform content type that was not deleted in the process.
I have no clue on how I might debug this as no error fire at all.

The 6.x branch is receiving critical bug fixes only.