Closed (fixed)
Project:
Webform Entity
Version:
7.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
24 Oct 2011 at 12:02 UTC
Updated:
24 May 2013 at 19:01 UTC
Is this module to make webform as an entity and use the core fields module, rather than the Webform approach?
Comments
Comment #1
tizzo commentedPartly right. This module makes webform submissions into entities that may use field api fields in addition to webform components. For the reasons documented in #118984: Field API based rewrite of webform module moving to fields for storage of webforms is a Bad Idea™. This project provides a Field API powered base form to which normal webform components are added.
Comment #2
webankit commentedPlease see this module too and see if they can be collaborated http://drupal.org/project/fse
Tough both modules do the same thing but the fse has a different approach, please read http://drupal.org/node/1326216.
Comment #3
webankit commentedComment #4
rogical commentedGuys may have a look at Entityforms, very useful.
Comment #5
tizzo commentedEntity forms solves a different problem. The module was created for a site that has many many many forms where the reusability of form api fields was a big problem in maintaining a site that had hundreds of forms with dozens of fields. The point of this module is to create a base form that has a set of fields and to augment that on a one-off basis with webform components that are not reused. Same issue with FSE.
Anything that doesn't support one-off form components doesn't address the need this module was created to satisfy.
Thanks!
Comment #6
tizzo commentedmarking fixed.