Associate to nodes not working

There is no "associate" between two separate nodes. You have to webform-enable the blog content type at admin/settings/webform, then a "Webform" tab will appear on all blog pieces of content. You have to build the webform directly as part of the piece of content you're viewing.

If you'd like to keep them separate (say, optionally attach a webform node to a blog post), you can do so with a CCK Node Reference Field, and then you don't have to enable webforms on blog content at all. It depends on what you're trying to accomplish. If the webform is a central part of the piece of content and you're going to be using it on every piece of content within that type, you should webform-enable that type. If it's an occasional, "we might need to attach a form to this type", you might be better off with a Node Reference.

Hello,

@quicksketch - what do you mean by "you should webform-enable that type".

For example i want to integrate a certain Webform into a certain Node type (ex. Page). Can't i use a tag or accomplish this modifying the .tpl.php file ?

Thanks a lot!

I think I already explained it:

You have to webform-enable the blog content type at admin/settings/webform, then a "Webform" tab will appear on all blog pieces of content.

You just visit admin/settings/webform and check the checkbox for the type you want to enable it on. You don't need to add it in your tpl.php files at all, if webform has been created on that node it will show up.

Hi,
I am also a little bit confused.
My goal is to give the users the ability to feedback on every node of my site. I do not want a specific webform for one node, but for the whole nodetype? This webform submission should automatically be filled with "parent" node title.
Is this doable please?

Thanks a lot in advance for your reply!

greetings,
Martijn

Re. webform enabling: I was a little confused about how this feature would work until I tried to use it -- I also thought that it would entail attaching or associating a webform node to another node, instead of just attaching a form to a node.

I think it may have been due to confusion over how the term "webform" was used. It used to refer to the content type; now it refers to both the content type and to the forms, which are independent of content type. Which is a great enhancement, BTW, but from outside the project it leaves me wondering why you need a webform content type at all anymore.

If questions like this persist, maybe you could think about trying to differentiate the two things more in the documentation.

A "webform" is the actual form itself that is exposed to the end user. "Webform-enabling" a content type means adding a front-end form to that content type. It just so happens that Webform module creates a content type called "webform" for you and webform-enables it by default. If you want to confuse yourself you can actually turn OFF the webform functionality on the webform content type, and instead turn it on story or page.

So you don't at all need a webform content type in the 3.x version. It's just that most people will expect to get a new content type automatically, just like you would with poll or blog modules, so Webform module creates and enables this type automatically for you.