Closed (fixed)
Project:
Webform
Version:
7.x-3.17
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
24 May 2012 at 01:08 UTC
Updated:
28 Jul 2012 at 06:07 UTC
From looking at some of the features Webform offers, I got the impression that if I created a custom content type, I could use this information to later generate a form based on this information, without later having to specify all the form items all over again.
I defined 5 basic content types:
CType1
CType2
CType3
CType4
CType5
In the usual manner under Admin >> Structure >> Content types, and specified ~ 50 fields in each one. Now, client wants to be able to enter the data for CType1 on 3 different forms (not multipage forms) so I’d like to create separate forms from the content info already defined (something like:
CType1
Form1
Form2
Form3
Etc, and place each one in its own block. Then with the form and the info defined, I could put the appropriate form out for them to fill in/update particular groups of information. (Information display could happen using Views for the appropriate fields.). Any suggestions/comments? I’ve got the feeling I’m just looking at this in the wrong way.
Using Drupal 7.12 with Webform7.x-3.17 and Arrange fields.
Comments
Comment #1
quicksketchNo, Webforms are *content* not *types*, and there's little relationship between the two. There isn't any way to convert content types into Webform forms because they have different features and options.
Comment #2
fejn commentedO.K. My miscommunication.The reason I was associating them is that on some form, I can specify whether Webform is to handle CType1; when I told it to handle that Content type (in addition to Webform); it allowed me to format the Content type data entry form. What I'd been hoping is that I could format the Content form with Arrange-fields/Webform, & then clone the form & produce the other 3 forms by just deleting the elements from that Ctype that I didn't need to support the particular form.
Thanks for the comments.
Comment #3
quicksketchI think you're misusing the word "Content Type". You can't ever "format the Content form with Arrange-fields/Webform". Webform forms are not the same thing as Content forms.
The content form (or node form) is what you see at node/add/article for example. The Webform form is what you see at node/x (where x is the NID of a webform).
To configure the content form you configure the content type, which lives at admin/structure/types. To configure a Webform, you go to node/x/webform.
Essentially content forms are administrative. Webforms are displayed on the front end publicly.
That said, you *can* enable Webforms on multiple content types (say both "Webform" and "Page" content types). You can also use the Clone module to copy the Webform nodes, and each node is completely independent of the other one. You cannot clone content types at all (that I'm aware of).
Comment #4
fejn commentedThanks for the clarifications. It has helped me refocus my efforts. This whole situation arose because my client doesn't want to fill out the Content forms generated when I defined the content type; my next thought was to try and build the equivalent of the Content form using Webform.
I've pretty much been able to do that, except that I don't know how to allow uploading of images through Webform. I suppose I could specify the component type as file, but I don't know if the file field will handle that.
Any suggestions on alternate approaches??
TIA,
Jeff
Comment #5
quicksketchYou can certainly allow users to upload images through the file component, but it won't actually display as an image directly inline anywhere. Webform submissions aren't really intended to be displayed publicly. Though if you like you can always theme the display of the file component or of the entire submission, though such approaches are outside the normal support of the issue queue.
Comment #6
quicksketchClosing after lack of activity.