Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Is this module to make webform as an entity and use the core fields module, rather than the Webform approach?
Is this module to make webform as an entity and use the core fields module, rather than the Webform approach?
Comments
Comment #1
tizzo CreditAttribution: 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 CreditAttribution: 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 CreditAttribution: webankit commentedComment #4
rogical CreditAttribution: rogical commentedGuys may have a look at Entityforms, very useful.
Comment #5
tizzo CreditAttribution: 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 CreditAttribution: tizzo commentedmarking fixed.