By dtfortier on
I am trying to create a process where people would fill out a "biography" form (webform), submit the form, then this form's content would populate fields for an existing content type.
What I have is a "biography" content type, which has pre-existing field types ready for content. Internally, administrators are currently just manually entering content from a word document. So to save time, I'd like to be able to have individuals who would like a biography to be able to access this form (webform), fill it out, then click submit. To then which would "submit" or populate the matching "biography" content type fileds.
Would a task like this be possible to conquer?
Comments
Why not have users directly
Why not have users directly create the biography content type and have default to not published.
Possibly....but...
That idea did come about, but we'd really like to try an stay away from creating new/more user logins for this. The profiles essentially already exist. And new ones are created when a new employee comes on board. And that's no handful, there's at least a good couple hundred of these particular employees that would need access as a user if that were the route I were to take. So I'm hoping to find a way a way where webform can just speak to a cck type/form and fill in the blanks
You can allow anonymous users
You can allow anonymous users to create content, no need for extra users.
Right. However, the situation
Right. However, the situation is a bit more complicated I guess. We don't exactly want just anyone to be able to come in and create a biography. They are employees. And select employees at that, so not even just anyone within the institute should be able to go in there and create a biography. The simple solution here would seemingly be to create a user login for each of these select employees, however that brings me to the road block where we're trying to keep away from creating unique ID's for each of these employees. So in a dream world, I'd like to have webform field content populate cck fields on submission
I am confused, since anybody
I am confused, since anybody would be able to fill in the web form OR create the content, if the content type is unpublished by default, the end result is pretty much the same and more straightforward using just the content type. Either way you may get unwanted submission, with a content type you can just delete it, with webform ignore the entry.