If I edit the field display of the content type Webform, I see "body" and "webform" as the two content types. In any other content types I create, however, I don't manage to add this part "webform". How should I do this?
Is there a way to add the webform to this view that I haven't figured out? Is there a way to make a content type that has a webform embedded (with its own field set, etc.)? Am I supposed to just make everything content type webform, and if so, how to deal with different fields on different webforms?
I'm clueless how to make different page types with fields + a webform. E.g. create events with date of the event (not part of the form) + a subscription form for participants, without requiring all other webforms on the website to have an event date (e.g. contact forms don't need one).
Comments
Comment #1
quicksketchYou can Webform-enable any content type you like on the Webform settings page located at admin/config/content/webform.
Comment #2
P3t3r commentedAha, that worked, thanks!
Out of curiosity, would it be difficult to add some text into admin/structure/types/manage/*/display (with * the content type) to tell the user that this can be added in admin/config/content/webform?
Currently this ability seems a bit hidden (at least it didn't come to my mind to go look there). In the past I've just modified the existing Webform content type, since I only needed one type back then, and I presume there will be more users with this confusion.
Comment #3
quicksketchI don't have any exact numbers on this, but I speculate that upwards of 90% of sites only use the built-in Webform content type and don't Webform-enable any other types, so burdening the interface in other parts of Drupal doesn't seem desirable. In truth if Webform behaved like most other Drupal modules, it would put the option to Webform-enable the type at admin/structure/types/manage/* (similar to the way you enable Scheduler, Flags, and other modules). But the rarity of multiple types I think warrants the module's current settings location.
Comment #4
P3t3r commentedI think the rarity of the multiple types (if correct) is partly a consequence of its location. If I didn't really really need two webform types for the website I'm working on, I'd never even have known that this was possible! Just pointing out...
Well anyway, thanks for the support, I'm happy to know this now!
Comment #5
codemuncher commentedIts not very usefull. I mean when i see the form I dont see the content type's fields. i dont see the fields of the content type inside webform either. It would have been useful to translate pages of certain types and have them used as webform as well. Webform translation means having 2 lists of fields since field translation does not work well at all.
Too bad webform is not well integrated into drupal 7. It's more like a guest who brings his own table, chairs and wine then sits with us and acts like everything is normal ;)
Comment #5.0
codemuncher commentedtypo
Comment #6
danchadwick commented